The Atari Compendium/The Atari Compendium (Toad Computers) (1994).iso/files/umich/telecomm/trn2401.lzh/install.lzh/TRANSBBS.DOC

Text File | 1993-05-15 | 216.1 KB | 6,993 lines

                             Transcendence BBS

                 Copyright © 1989 - 1993, Southern Software

                               Programming By
                                David Brown
                                    and
                                Wayne Watson























     All rights reserved. No part of this manual may be reproduced by
     any means (electronical or mechanical) without prior written
     consent from Southern Software.


                                    PREFACE

         The Transcendence BBS package was originally conceived by David
     Brown in 1986. He began researching BBS programs, how they work, and
     how they don't work. At this time he did not know the first thing
     about computer programming (His first computer was a 520ST, in Oct.
     1985). He began teaching himself how to write this type of software by
     programming online "door" software.

          In mid 1987 He began work on the "STark" BBS program. Soon he was
     joined by Jason Dickens. They worked on the program for about 2 years,
     and due to some problems, had to terminate their joint-effort. For a
     one year period he was without the source code to the STark BBS
     program. Since BBS programming was his work away from work, He started
     a new one. This program was entitled "STairway" (it was never
     completed). He then obtained the source code to STark, and used the
     two programs to create what is now "Transcendence."

           Soon after starting on Transcendence, he asked me to help re-
     write many of the old STark routines. I began work on the File Areas
     and wrote the transfer protocols along with many other support modules
     for the BBS.

          Since David and I started working together, we haven't stopped to
     take a breath. The program has gone through massive rewrites and
     modifications. The current program is beyond what we ever thought we
     could do. We feel that we have succeeded in creating the most
     flexible, powerful, user-friendly, and sysop-friendly BBS system ever.
     Our sysops seem to agree.

          In January, 1993, David decided to get out of development of
     Transcendence and asked me to take over marketing, selling, updating
     and supporting the program. I will miss the times that we spent
     working together. David has taught me a lot about programming
     telecommunications software and other things. It was a very good
     partnership. Although we keep in touch, it will not be the same. I
     wish David the best of luck in all his efforts and in life. Thanks
     David for so much!

          I wish you luck in your adventures as a Sysop and hope that
     Transcendence will make your experience a pleasant one.


                                                       Wayne Watson
















                                     - 1 -


                                INTRODUCTION

     PRECAUTIONS

       In development of the Transcendence BBS package, we have
     attempted to create a bug-free system, with no harmful side affects.
     Unfortunately, with a program of this size, it is impossible for us to
     predict every configuration a sysop could create. Due to this we must
     ask you to use the software at your own risk.  We can not be held
     responsible for damage (Or loss) of data, hardware or software.

       There are NO backdoors into the BBS program. We feel that if we want
     access on your system, then we can apply for an account just like
     everyone else. This is for your protection.

     SUPPORT POLICIES

       One of the main benefits to the Transcendence BBS system is our
     support. All updates to our software are 100% free. You pay only the
     phone bill, or postage. We are planning a modular version of the BBS
     system, there will be a minimal update fee for this, but it will be a
     one time fee.

       We rely on our sysops to give us feedback on the program. A lot
     of the features in the software are features requested by one of our
     sysops. Unlike other companies, we actually listen to our clients.

       You can obtain your free updates by calling one of our support
     BBSs, or by mailing a Self-Addressed-Stamped-Envelope, with a disk
     enclosed to me.

        We encourage you to give us suggestions. We can only improve the
     program if you let us know how. We also need to know if something is
     not working correctly. If you find any "bugs" in the software, let us
     know. We can't fix 'em, if we can't find 'em!

     Southern Software
     c/o Wayne Watson
     1129 lake Cunningham Rd.
     Greer, SC  29651

     Data:  [phone] 14.4k Supra v.32/v.42bis
     Voice: [phone] or [phone]

     NOTE: Since I have a full time job, there may be times when it will be
     hard to get ahold of me. I hope you will be patient and understanding
     during those times. I do what I can with the free time I have to work
     on the BBS and to help my customers. Also, since I only have the one
     phone line strictly for my use, I use it for other things also. I also
     only have the one computer to do real development on so the BBS may
     be down at times. I will usually quit what I am doing and boot the BBS
     for you to use however.

       I am also on GEnie. If you have a GEnie account, you can reach me by
     Email at the address R.WATSON15. We also have a Topic in the BBS
     RoundTable for support. Please drop by to visit.




                                     - 2 -


     SYSTEM REQUIREMENTS

          To run the Transcendence BBS System you need the following
     hardware:

          o 520, 1040, Mega ST, STe, or TT
          o At least 1 meg of RAM
          o A modem (Hayes Compt. preferably)
          o A hard drive with at least 20 megs of space
          o Color or MONOchrome monitor (Medium & high resolution only)

          The following software/hardware is preferable, but not required:

          o Printer
          o XYZ external Zmodem protocol
          o Software or hardware backup utility
          o Micro Emacs Editor (Remote version)
          o 2.5 or more megs of RAM
          o TOS 1.4 or above

     COPYRIGHT NOTICES

          The Transcendence BBS program, all associated programs written by
     Southern Software and this manual are copyrighted by Southern
     Software. Unauthorized reproductions of those files, or the manual is
     strictly prohibited by international copyright laws. This software is
     not allowed to be "rented" or "borrowed". Such acts are clearly a
     violation of copyright laws. We reserve the right to deny updates &
     support to anyone, for disobeying the copyright.

          We have always provided you with a non-copyprotected BBS package,
     with the hopes that you will not distribute it without our written
     permission.  "Pirating" software, as illegal copying is often called,
     only hurts the authors of the program, and those who paid for the
     program.  Please do your part and do not support software piracy.

          All associated files, programs or documentation not written by
     Southern Software are copyrighted by their authors.






















                                     - 3 -


     YOUR MASTER DISK

       With this documentation you should have received two disks. The
     disks are in DS/DD format.  If you can not read that type of disk,
     contact Southern Software to get a replacement.

          Before doing anything else, make backup copies of all your disks.
     Use the backups when possible, store the originals for safekeeping.
     If you have trouble creating a backup copy of your original disk
     consult your Atari owners manual for "Duplicating" disks.

          These disks are not setup to run files from floppies!  They are
     designed to first be copied to a hard drive, and then used.
     Transcendence was not made to run from floppy systems, although it
     should be possible to run a VERY small BBS from floppies, we do not
     recommend it.

     DISK ONE  : Contains the BBS and associated files in LZH form
     DISK TWO  : Third party programs.  These are programs
                 written by people not involved with the development
                 of our software.

     NOTE: Any of these disks may contain a README file in their root
     directory, if so it probably contains updates to this manual, or
     important information about something on the corresponding disk.

     YOUR KEYCODE.DAT FILE

          The file called KEYCODE.DAT is a private-key type of file.  In
     this file is your name, and serial number. This file is not to be
     given out to anyone, for any purpose. If someone gets a copy of your
     KEYCODE.DAT file please contact Southern Software for a replacement
     copy. (We can prevent 'stolen' KEYCODE.DAT files from working.) We can
     also find out what information is in the KEYCODE.DAT file when/if we
     log onto your system. This is not a back door to the program, it is
     just a special key sequence that will display the information.
























                                     - 4 -


                         Chapter 1: Creating a New BBS

       Now for the fun part, creating your own BBS!  This chapter explains
     how to set up a new BBS, using our GEM System Editor.  We assume you
     already have a working knowledge of Atari's GEM environment.  If you
     have never used the GEM environment, please refer to your computer's
     owners manual for details.

       While we have attempted to make this chapter easy to understand,
     please remember that Transcendence is LOADED with options.  Almost
     everything is configurable, and optional.

     PREPARING FOR YOUR BBS INSTALLATION

       Installing your BBS can be a very short process, or it can take
     hours. This will depend on how many message bases and file areas you
     want, and also on many other things.  This chapter will attempt to
     make this process easier (or shorter) by giving you a few tips on what
     you should do before beginning the installation.

       There are many things to consider before you begin the installation
     process.  Many new sysops overlook these details, we hope we can
     prevent you some heartache down the road.

       The Transcendence BBS System takes up a lot of Hard Drive Space.
     Before installing the BBS you must make sure you have enough hard
     drive space.  To do this, delete old files you do not need and copy
     files you do not use often to floppy.

       If you were to create a BBS allocated for 100 users and five message
     bases (100 messages each, 20 lines long), that would take about 2-3
     megs of hard drive space (It still greatly depends on other factors.)
     Hopefully that will give you some idea of how much room you will need.

       You can tell Transcendence what partitions to use for each type of
     data it creates/uses.  For example, you can have your download files
     on drive C & D, your message base files could be on drive F, and all
     other files on drive H.  While you clear off your hard drive space
     take into consideration where you want your different types of data.
     You can use the same partitions for all of the data files the BBS
     uses, or use many different ones, it all depends on what you want.
     When doing this remember that the partitions dedicated to file areas
     will eventually take up the most space.

       Transcendence uses "Pre-Allocated" data storage.  That is, whenever
     possible the BBS makes all data files to their full size.  This makes
     file access faster, and reduces the chance of DISK FULL errors (No BBS
     can prevent DISK FULL errors, only the Sysop can!).  Whenever
     Transcendence has to create a file, it picks the drive with the most
     space (assuming you have it set up to use more than one drive).










                                     - 5 -


       Transcendence uses a lot of different types of data files for
     storing and retrieving information from your hard drive.  It is
     possible for Transcendence to use hundreds of files.  Since there are
     so many files used by the BBS, we had to come up with some way to
     organize them.  The method we use is a storing each type of data in
     its own folder.  In addition all of the folders used by the BBS may be
     contained in a "Main" folder.

       If you choose, you can bypass the "main" folder, and have all of
     your data folders right on the root directory of your drive.
     Although, for several reasons we do not recommend this.  Mainly,
     throughout the entire manual we always use a main folder in examples,
     and explanations.  Also, if you make a mistake during your
     installation, and want to start over you have to delete each folder
     individually, whereas if you used the main folder you could delete
     everything by only deleting the main folder.

       In this manual we will refer to the different folder names by their
     default names, which are:

     Main Folder:        TRANS
     Data Files:         DATA
     Text Files:         TEXT
     Message Bases:      MESSAGE
     File Areas:         FILES
     Backup Files:       BACKUP
     Module Files:       MODULES
     Fmail/Fmessages:    FMAIL
     Temporary Files:    TEMP

       When you create your BBS these are the default names for the
     different data types.  You may change the folder names, but again, we
     do not suggest it.  In this manual we will refer to the different
     folders names by their defaults (listed above), which may become
     confusing if you have changed them.

























                                     - 6 -


     HOW TO LAYOUT YOUR NEW BBS

       Before you actually begin the installation, you should consider
     exactly how you want your BBS setup.  For example, how many message
     bases you want, and how many file areas you want.  There are several
     other things to decide also.  Ask yourself the following questions,
     and write the answers down so you can reference them while creating
     your BBS.

     o How many message bases do I want?
       - What are their names (30 characters max.)?
       - How many messages will each base handle (10-512)?
       - How many lines can each message be (5-256)?

     o How many file areas do I want?
       - What are their names (30 characters max.)?
       - How many lines can be in each description (2-256)?
       - What will the folder-name be for that file area?

     o How many users shall I allocate space for?

     o Should I let my users define their own macros?

     o How many Email messages should I make space for?
       - How many lines should I allow for each Email message?

     o What partitions should I use for each type of data?
      - Different Data types: Data Files, Message Base, File Areas,
        Temporary Files, Fmail/Fmessage Files, Text Files, Backups,
        Modules.

     o Decide which partition will be your "Main BBS partition", this
       is the drive your will actually be running the board from.

       Of course there will be a lot of other questions you will have to
     answer while creating your BBS.  It might be wise to read this chapter
     before actually creating your BBS.























                                     - 7 -


     QUICK SETUP

       Copy the TRANS.LZH, LHARC.TTP and the INSTALL.PRG file onto the
     drive that you are going to install the BBS on. This should be where
     you want all of your text files, data files, BBS program, etc. on.

       Now, run the install program and follow the prompts. Everything is
     pretty much self explanatory. Once this phase is complete, you can now
     run TRANSBBS.PRG. You may copy the LHARC.TTP file to your MODULES
     folder. This is version 2.01L by Yoshi Questor.

       The BBS will come up and go through some initial loading of files.
     It will then come to what is called the 'WaitCall Screen'. At this
     point, it will log on and ask you if you wish to join the BBS. Enter
     in the information. This will set you up as the very first user in the
     USERS.DAT file. Once you have entered the information, the logon
     process will continue. You will then see an Auto-Informer message that
     a New User has logged on. At this point, just select 'V' for Validate
     and enter in 100 as the Mask to apply. The Auto-Informer will be
     explained later.

       You should now log off. The BBS is now setup in it's default mode
     and is available for use. You might also want to set up record #2 for
     your use. Just select 'D' at the WaitCall Screen and type 'New' at the
     prompt. You will go through the New User setup once again and be
     assigned record number 2. When you log off, just select 'A' at the
     WaitCall screen and you will once again be informed of a New User.
     Just repeat the process above.

       That is all there is to it. You now have a BBS system set up and
     ready to go. Of course, there are things you will want to change and
     add. Just read this chapter through and most of the settings for the
     system will be explained.



























                                     - 8 -


     CREATING A NEW BBS

       If you want to start completely over and create a BBS from scratch,
     then delete the TRANS.DAT file. If you have files that you would like
     to keep that are in the FILES folder(s) (files uploaded, etc.), then
     copy them somewhere safe. If a file exist when you are setting up the
     BBS, you will be asked if you want to overwrite it.

       Once you have done this, you can create a New BBS setup. Just run
     the SYSEDITG.PRG and follow the prompts. Just select CANCEL when the
     BBS ask you to select the TRANS.DAT file to load and answer Yes to the
     question asking you if you are creating a new BBS.

       Please read over this chapter. It contains a lot of important
     information that is necessary for the proper operation of the BBS.
     This will help you in your setting up of New BBS also.

       The MASKS.DAT, COMMAND.DAT and the PROTOCOL.DAT files are pre-
     configured for you. You may want to copy them somewhere else as a
     backup.








































                                     - 9 -


     THE SYSTEM EDITOR

       The System Editor is one of the most important parts of the BBS.
     With it, you control how your BBS acts, reacts and looks. It is the
     gateway to the BBS. Go ahead and run it and I will try and take you
     through it.

       You will need to have the following files in the same directory as
     the System Editor (SYSEDITG.PRG) program. If you want the program to
     automatically load in the TRANS.DAT information, then place these
     files in the same directory as the TRANS.DAT file.

     SYSEDITM.RSC - The Monochrome Resource file.
     SYSEDITC.RSC - The Color Resource file.

       After you run the System Editor, you will be presented with a dialog
     box with some general information. When you are ready, select OK or
     hit RETURN.

       The BBS program will load in the required information (assuming it
     exist) and tell you if there is anything it could not find. if the
     program does not find the TRANS.DAT file, it will ask you to locate
     this file by presenting you with a fileselector. Once the information
     is loaded, it will present you with a GEM Menu Bar. We will go through
     this menu from Left to Right, Top to Bottom.

       The Menu Bar titles are in BOLD UPPERCASE. The selections within
     each title are in normal UPPERCASE. Options on alternate menus within
     these selections are in ITALICS UPPERCASE.  Any other selection, etc.
     is in Bold Upper/Lower case. These distinctions will not show up in
     the disk based version of this chapter.

       Keyboard shortcuts to the menu entries will be listed to the right
     of the option. The diamond shaped character means to hold down the
     Alternate key while pressing the letter next to it. The ^ character
     means to hold down the Control key while pressing the letter next to
     it.

       Anytime you see a triangle beside a selection, it is a mouse
     selectable field. You click on it with your left mouse button. Some of
     these fields may also be a combination of mouse selectable and text
     fields. You will be able to tell the difference.

       Anytime you see a time field (On At: 00:00:00  Off At: 00:00:00), a
     time of On At: 00:00:00  Off At: 00:00:00 will tell the BBS this
     option is on all the time. If you have On At: 01:00:00  Off At:
     21:00:00, then the option will be on from 1:00 am till 9:00 pm. All
     times are in military time. 21:00:00 refers to 9:00 pm. To find out
     what a time is after 12:00 midday, just subtract 12 from the number
     (21 - 12 = 9).

                         ********* Warning *********
       If you plan on doing any major modifications, it is suggested that
     you backup ANY data you plan on editing. This is just a precautionary
     measure. It will allow you to restore things if something goes wrong.
     I am not saying I know something will go wrong, I just feel better by
     warning you. Things happen you know.



                                     - 10 -


     DESK

     This is where you will find your Desk Accessories and the About Me
     dialog box.

     SYSTEM EDITOR  (ALT-A)

     This will bring up the About Me dialog box. This will tell you the
     version number of the System Editor, ordering information and other
     information.

     FILE

     This is where you Load and Save the TRANS.DAT file and Quit the
     program.

     LOAD TRANS.DAT  (ALT-L)

     This option will allow you to Load in a TRANS.DAT file. When selected,
     it will bring up a file selector for you to choose TRANS.DAT file. By
     providing you with a file selector, it allows you to load in a
     TRANS.DAT file that may not be located in the same directory you ran
     the System editor from.

     SAVE TRANS.DAT  (ALT-S)

     This option will allow you to Save the TRANS.DAT file. When selected,
     it will bring up a file selector allowing you to choose where to save
     the TRANS.DAT file. It will default to the location the System Editor
     was ran from.

     If the program asks you if you want to Save a particular file when you
     exit that setup area, then that data is not part of the TRANS.DAT
     file. This will include the data for the Command Tables, Protocols,
     Macros, Events and Masks. If you edit these areas, then you will not
     need to Save your TRANS.DAT file before you exit the program.


     QUIT  (ALT-Q)

     This option allows you to Quit the System Editor. If the program
     thinks you have changed some information that belongs in the TRANS.DAT
     file, it will ask you if you want to Save the TRANS.DAT file before it
     actually quits. This is just incase you forgot to Save the file first.
















                                     - 11 -


     EDIT

     This is where you will find the majority of the setup selections.

     MESSAGE BASES

     This is where you edit or setup your Message Bases. You will be
     presented with another dialog box with some options.

     EDIT MESSAGE BASES

     This option will allow you to edit the information for a Message Base.
     You will be taken to the first Message Base and be presented with
     another dialog box that contains the information for that base.
     Following is a description of those options.

     Name

     This is the Name you want to give to the Message Base. This name will
     be displayed to the user when selecting a message base to go to, etc.

     Maximum Messages

     This is the maximum amount of messages you want to have in the message
     base. Once the message base reaches this amount of messages, it will
     roll over. If you assign 50 message slots and the program reaches 50
     messages in the base, the first message will then be deleted and the
     next message (# 51) will take it's place. The higher the number of
     maximum message you assign, the larger the data file.

     Maximum Lines

     This is the maximum number of lines that a user can enter as a
     message. Anything past this point becomes an Extended message and
     will be saved in the EXTENDED folder. The higher the number, the
     larger the data file.

     ** To calculate the amount of space a Message Base will take, use this
     formula. Max. # Messages * Max. # Lines * 75. If you allowed 50
     messages and 20 lines per message, the Message Base data file would
     take up 75,000 bytes (50 * 20 * 75 = 75000).

     Minimum Age

     The user's age must be at least this age before he/she can enter a
     message base. This is good in that if you have an Adult type Message
     Base, you would not want to have users under age to be able to read
     these messages.

     ** You may enter On or Off in the following fields or you can click on
     them with the mouse to toggle them On or Off. Upper or lower case is
     accepted.








                                     - 12 -


     Remote Message Ops

     This will tell the BBS whether or not to allow Remote
     Message Ops. Not used at the moment.

     Anonymous

     This tell the BBS whether or not to allow anonymous messages.

     Alternate Message Header

     This tell the BBS whether or not to use an alternate headers for
     message status (if available) or not. With the use of variable tags,
     you can design your own headers in a text file that includes Message
     number, Status, etc. Whatever you want. This relates to the file
     MHDR_xxx.TXT. The xxx is the message base number.

     Allow Any Name

     This tells the BBS whether or not to allow the user to post a message
     using any name he/she wishes. Obviously this should be a very
     controlled privilege and should not generally be used. There may be
     Message Base that this would be allowed but, not usually.

     Allow ESC Codes

     This tells the BBS whether or not to allow the use of ESC codes in a
     message. VT52 text and graphics use ESCape codes to control text
     color, background color, etc. With this off, the program will filter
     out the ESC character and display the control number. With this option
     on, the user could include VT52, ANSI, etc. graphics in a message.

     Allow Variable Tags

     This will allow the use of variable tags within a message base.
     Variable tags are used in the text files you create also. For
     instance, if you wish to post a message and each time a caller logs on
     and reads that message, if you place the variable tag for the user's
     name in the message, then the user's name would appear in the
     message and it looks as if it is a personal message to that user. This
     can also be a touchy feature. If a user post a message with the
     variable tag for the user's password and that user logs on and reads
     the message, it will put their password in the message and it appears
     that anyone would be able to see it when, in reality, each user will
     only see his/her password. It can upset some people if they do not
     know what is going on.

       Once you have all the information the way you want it, select Next
     to go the next Message Base, Prev to go to the previous message base
     or Exit.

       The program will then create all the necessary files. You can page forward
     or backwards through all the message bases. The information will be
     remembered. If you make a total mess of things, you can go back to the main
     menu (menu bar) and load the TRANS.DAT file again and it will restore
     things back to the way they were.




                                     - 13 -


     REFORMAT 1 BASE

     This option will allow you to Reformat, Convert or Restore a Message
     base. When selecting this option, you will be presented with a list of
     available Message Bases to choose from. Once you make your selection,
     you will be presented with the dialog box to change your Message Base
     information. Once you have it set the way you want, you will be
     presented with a dialog box giving you 3 options. When you choose one
     of the 3 options, you will be asked if you are sure and given the
     chance to abort by selecting NO.

     Reformat

     This option will allow you to reformat your Message Bases. This will
     delete ALL messages, etc. from this base. If you changed any of the
     information in the setup dialog box, it will create the new files
     based on this information. You should make sure this is what you want
     to do.

     Convert

     This option will allow you to convert your Message Bases to a new
     layout (more messages or longer messages) without loosing your data.
     If you wanted to increase the number of lines a user can enter, then
     you would enter the new number on the setup screen and select exit and
     choose Convert. When you convert to a higher number of lines, all the
     messages that are not extended messages will be reserved as the same
     type of message it is. If you convert to a lower number of lines, the
     messages falling outside the new range will be converted to extended
     messages. If you convert to a lower number of messages allowed, those
     falling outside the range will be deleted.

     This option will make a backup of your Mxxx.DAT and Mxxx.SPD files so
     that you can do a Restore Original later on. The information is read
     from the backups and placed into the new files. These files will NOT
     be deleted by the program. It is suggested you write down the layout
     of the current Message Base in case you need it later on if you do a
     Restore Original.

     Restore Original

     This option allows you to restore a previously Converted Message Base.
     To do a Restore Original, just delete or move the current Mxxx.DAT and
     Mxxx.SPD files and rename the Mxxx.DA file to Mxxx.DAT and Mxxx.SP to
     Mxxx.SPD. You would then run the System Editor and go through the
     motions of reformatting a Message Base. When you come to the setup
     screen, enter the old information (hopefully you wrote it down
     somewhere) and select Exit. You would then select Restore Original and
     Yes (if you really want to do it). Once this is done, the program will
     calculations based on the info you gave it and if all is correct, the
     old information will be restored.









                                     - 14 -


     REFORMAT ALL BASES

     This option is like the Reformat 1 base but, it will go through each
     and every base until it is finished. You have the same options
     available to you as above. It will start with Message Base 1. Once you
     finish editing the information on the setup screen, select Exit and
     you will be presented with the Reformat, Convert, Restore Original
     dialog box. Once you make your choice, you will asked if you are sure.
     Once it is complete with what it is supposed to do, you will taken to
     the next Message Base to do it all over again.

     EDIT A BASE

     This option is much like the Edit Message Bases option except it gives
     the choice of the Message Base to start editing at. You can still page
     forward or backwards to the other message bases using the Next and
     Prev options.

     DELETE A BASE

     This option allows you to delete a base. You will be presented with a
     list of Message Bases to choose from. Once you make your selection,
     you will be asked if you are sure. Once you delete it, the data files
     are deleted so there is no turning back once you select Yes. You will
     then be asked at what user number to start the change for access to
     that base. This allows you to bypass the first 2 records that are
     reserved for you (the Sysop). Once a base is deleted, all the other
     bases will be renumbered and the associated files will be
     adjusted/renumbered.

     INSERT/ADD A BASE

     This option will allow you to Insert a Message Base between 2 message
     bases or add it to the end. You will be presented with a list of the
     currently available Message Bases. Choose where you want to place the
     new base. If you Insert a message base, it will place it BEFORE the
     number you choose. If you wanted to Insert the base between base 1 and
     base 2, you would enter 2. You will be asked for the standard
     information. Select Exit when you are done and you will be asked if
     you are sure. You will then be asked at what user number to start
     changing the access to that base. You can bypass the first 2 records
     which are reserved for you (the Sysop). If you Insert a base, all
     associated files from that point on will be renumbered.

















                                     - 15 -


     RESET MESSAGE COUNTERS

     This option will allow you to reset the user's counters (high message
     read) to the number you enter. You will be asked if you are sure you
     want to do this. You will be presented with several options. Make sure
     you read the prompts as it will give you some information. Just hit
     RETURN if you do not want to go through with this and answer NO to the
     question Are you sure?.

     ALL counters

     This will allow you to reset the user's counters in ALL the message
     bases to a specified value.

     One Counter

     This will allow you set the user's counter in 1 message base. You will
     be presented with a list of the currently available message bases to
     choose from.

     Some Counters

     This option will allow you to reset the user's counters in certain
     bases. It combines the 2 options above. It will step you through each
     message base allowing you to enter a number to set the counters to. If
     you do not want to change the counters in that base, then just hit
     return and answer NO to Are you sure?. The program will then go onto
     the next base.

     CREATE MULTIPLE BASES

     This option will allow you to do a MASS creation of Message Bases. It
     will ask you how many message bases you want and then ask you for the
     information on the setup screen. The program will apply this
     information to ALL the bases it creates. You can then go back and
     change this information in the ones you want to. Just do a Edit A Base
     or Edit Message Bases and enter the information. Select Exit and if
     you changed the information, it will ask you if you want to reformat
     the message base. Just continue until you are finished editing all
     that you want to edit.

     EXIT

     This option will take you back to the Main menu.
















                                     - 16 -


     EMAIL

     This option will allow you to edit the Email section. You will be
     presented with a dialog box with 3 options.

     RENAME EMAIL

     This will allow you to Rename your Email section.

     REFORMAT EMAIL

     This will allow you to reformat your Email. You will be presented a
     dialog box to enter the information in. Once you have entered the
     information, just select Exit. You will then be given the option of
     Reformat, Convert or Restore Original. These options work the same as
     explained in the Message Base section above. Once you make you choice,
     you will be asked if you are sure. Just select the appropriate
     response.

     EXIT

     This will allow you to exit back to the Main menu.

     Name

     This allows you to chose what you want to call Email.

     Max. Messages

     This will tell the BBS how many Email messages to allow. Once the BBS
     has this many Emails, it will not allow anymore until some are
     deleted. The larger the number, the bigger the file. 50 is a good
     number to begin with. If you expect a lot of Email traffic, then you
     may want to use a larger number. You can always increase it later.

     Max. Lines

     This will tell the BBS how many lines to allow before it becomes an
     Extended Email Message. This works the same as Extended Messages.

       Once you have Email set up the way you want, select 'Exit'. The
     program will then take you through the steps described above.

     Exit

     Allows you to Exit the setup screen.














                                     - 17 -


     FILE AREAS

     This allows you to edit your File Area information. You will be
     presented with a dialog box with several options. Most of these
     options work just like those described above in the Message base
     section. I will not go into as much detail as it is just duplicate
     information. A lot of the choices will take you through the same
     steps. The only difference is this is for the File Areas.

     EDIT A FILE AREA

     This will allow you to edit the File Areas. This option will step you
     through each File Area asking for the new information. Just select
     Exit after you edit the area and follow the prompts. If no information
     is changed and you either select Exit or Next, the program will just
     go to the next File Area or Exit back to the File Area dialog box. If
     it has changed, you will be asked if you are sure you want to do this.
     Below is the setup screen for the File Area.

     Name

     This is the Name of the File Area. This is the name that the users
     will see when they make their choice as to what File Area to go to.

     Folder

     This is the name of the folder that will hold all the files associated
     with that File Area. The files that are uploaded and the description
     files will go here. You will be asked if you want the program to
     create this folder. If it is already there, then there will be no
     problem if you say YES.

     Maximum Lines

     This is the maximum number of lines that will be allowed for entering
     a description. If it is set to 15, then only 15 lines of description
     can be used. You don't want to have too many lines but you also don't
     want to have too few lines. 10 - 15 lines is generally enough. In the
     File Area where I have ST Reports and Znets, I have it set to 15
     because the contents of that issue usually run about 11 lines.

     Minimum Age

     This is the minimum age of a user that is required in order for them
     to enter into the File Area. 0 = Any Age.

     Upload Level

     This is what level the uploads will default to if the user that
     uploads the file does not have the privilege of choosing/setting the
     upload level. The user must have this File Access Level before he/she
     can see it. If he/she cannot see it, then they cannot download it,
     etc. I have all my files default to 255 when uploaded. This means that
     only I or anyone with that access level (generally only those with
     sysop access should have this level) can see it until it has been
     validated/released by me. I do this by changing the level of the file.




                                     - 18 -


     Alternate Drives

     This option will allow you to set up different drives for that File
     Area. If you wanted you Atari St Utilities to go to DE, then enter DE
     here. Each File Area can have it's own drive partition. These drives
     MUST ALSO be in the File Area field in the Drives and Paths screen. If
     you choose DE for your partition for this File Area, DE must also be
     in the File Area field in the Drives and Paths section.

     The below settings can either have the words On or Off typed in them
     or they can be toggled On/Off by clicking on them with the mouse. It
     does not matter if you type it in upper or lower case.

     Remote File Ops

     This tells the BBS that Remote File Ops are allowed. Not used at the
     moment.

     The below settings with the exception of Auto-Compress will tell the
     BBS to ask for this information when a user enters the description of
     a file that he/she uploaded or when the description of that file is
     being edited.

     Anonymous

     This tells the BBS that a user can upload a file anonymously.

     Ask Computer Type

     This tells the BBS to ask for the Computer Type. If you have the
     COMPUTER.DAT file in the DATA folder, then that file will be displayed
     and the user will have to make a choice. If the file is not found,
     then they will be able to enter in anything they want. See the
     explanation for COMPUTER.DAT for further information.

     Ask Monitor Type

     This tell the BBS program to ask for Monitor type. If you have the
     MONITOR.DAT file in your DATA folder, then the file will be displayed
     and the user will have to make a choice. If the file is not found,
     then they will be able to enter in anything they want. See the
     explanation for MONITOR.DAT for further information.

     Ask Program Type

     This tell the BBS to ask for the type of program. It was designed for
     asking whether or not the file is a Utility, Application, Game, etc.
     You can use it for whatever you want. If the file TYPE.DAT is in the
     DATA folder, then it will display it and the user will choose from
     this list. If it is not found, the user will be able to enter in any
     information they want. See the explanation for TYPE.DAT for further
     information.








                                     - 19 -


     Alt. File Header

     This tells the BBS to look for FHDRxx.TXT (xx = File Area number) and
     display it. This is the header information where it tells all about
     the file. It includes things such as Filename, Filenumber, Uploader,
     Date of Upload, etc. You can create this file using any of the
     variable tags and put in the information you want. If it does not find
     this file, then the built in header will be used.

     Auto-Compress

     This will tell CLEANUP.PRG whether or not to compress files that are
     not already compressed. If you want files to be compressed (such as
     text files, etc.) during execution of CLEANUP.PRG, then set this field
     to on. The type of compression used is set in the Cleanup section.

     Ask File Type

     This tells the BBS to ask for the type of file. It was designed to ask
     if the file is an LZH (LH1), LZH (LH5), ARC 6.02, etc. type of file.
     If the file 'FTYPE.DAT' is found in the DATA folder, then the BBS will
     display that file for the user to choose from. If it isn't found, then
     the user can enter anything they want here. You can use this file to
     hold any kind of information you want.

       Once you have set up the File Area the way you want it, select
     'Exit'. The program will then create the necessary folders and files.
     You can also select Next or Prev to go to the next or previous File
     Area in order to edit it. Upon exiting using either option, if any
     changes were made, the program will respond and ask you questions and
     do what it is supposed to do.

     REFORMAT 1 AREA

     This option will allow you to reformat a File Area. You will be asked
     to choose the File Area and then you will be asked to enter the
     information. Once you have entered the information, you will be given
     the option of Reformat, Convert or Restore Original. These options
     work the same as explained in the Message Base section. The only
     difference is that if you Convert an Area to a new format and the
     number of lines is lower, then the file descriptions will be cut off
     after that many lines. There are no Extended file descriptions. You
     will be asked whether or not you want to do this.

     REFORMAT ALL AREAS

     This option will allow you to step through ALL the File Areas offering
     the same options as Reformat 1 Area. It will start at File area 1 and
     step through each and every File Area giving you those options. If you
     do not want to change anything, just select NO when asked if you are
     sure. This works the same as Reformat All Bases.









                                     - 20 -


     CREATE MULTIPLE AREAS

     This option will allow you to create a lot of File Areas at one time.
     You will be asked how many File Areas you want. You will then be asked
     to enter the information in on the setup screen. These settings will
     be applied to all the file areas that are created. You can then go
     back later and change this information on the File Areas you want to
     setup differently.

     EDIT AN AREA

     This option will allow you to edit a File Area. You will be presented
     with a list of available File Areas to choose from. Once you choose
     the area, you will be asked to enter in the information on the setup
     screen. If you change anything, you will be told this and asked if you
     want to reformat it. If you choose Yes, you will be given the option
     of Reformat, Convert or Restore Original. You will then be asked if
     you are sure. You can select Exit to quit editing or select Next or
     Prev to go to the next File Area or the previous File Area. Either
     way, if you change anything, you will be asked what you want to do
     before it goes to the next or previous File Area.

     DELETE AN AREA

     This option will allow you to Delete a File area. You will be
     presented with a list of available File Areas to choose from and then
     asked if you are sure. If you answer Yes, there is no turning back.
     You will then be presented with a choice of where to start at when
     changing the user's access. If you start at 1, then your (the Sysop's)
     access is changed. This will allow you to bypass changing access in
     the first 2 records which are reserved for you. If you delete a File
     Area that is before another one, the program will renumber all
     associated files.


     INSERT/ADD AN AREA

     This option will allow you to Insert a File Area. If you choose number
     2 for instance, then the File Area will be inserted BEFORE File Area
     2. to Add a File Area, just type in a number 1 higher than what is
     available. You will then be presented with the setup screen to enter
     your information in. Once you select Exit, you will be asked if you
     are sure. You will then be asked if you are sure. You will be asked
     what user # to start at when changing the access to this file area.
     You can bypass the first 2 records which are reserved for you (the
     Sysop). If you Insert an area, all File Areas above that number will
     be renumbered.

     EXIT

     This option will return you to the Main menu.









                                     - 21 -


     COMMAND TABLES

     This will allow you to setup your Command tables. This is where you
     define what command will be available to the user, etc. The are the
     Commands that will be available from the Main Menu, File Menu and
     Message Menu. You will need to know what the PROCEDURE names are.
     These are built in PROCEDURES that the BBS recognizes. You can also
     set up external programs, text files, etc. from the Command Tables
     also. Please refer to the Built in Procedures section for the names
     and explanations of these procedures. You should have gotten a
     COMMAND.DAT example file with the program. It is located in your DATA
     folder.

     You will be presented with a menu giving you 3 options.

     EDIT COMMAND TABLES

     This will allow you to edit your Command Tables. You will be presented
     with a menu with 3 options of editing Main Menu, File Menu or Message
     Menu. Choose which one you want to edit and you will then be presented
     with a dialog box with several options to setup the Command.

     RELOAD COMMAND TABLES

     This will allow you to reload the Command Tables from disk into
     memory. if you really make a mess of things and wanted to start over,
     you could just exit from the Command Tables and select this option and
     start over. This of course only works if you have not already saved
     the Command Tables.

     EXIT

     This will take you back to the Main Menu.

     Below is the layout of the Command Table screen.

     Keystroke

     This is the key that will need to be entered in order to use this
     command.

     Status

     This will tell the BBS whether the Command is On or Off. If you wanted
     to temporarily disable a Command, just click on Status and it will
     switch to Off if it is On or On if it is Off.














                                     - 22 -


     Type

     There are 4 type of Commands. Click on this field with the mouse and
     you will be presented with 4 items to choose from. Once you have
     chosen one of the below types, the program will return to the setup
     screen and the type will be in the Type field.

     Internal BBS Procedure

     These are the Commands built into the BBS. These built in procedures
     are listed in the Built in Procedures section along with an
     explanation of what each one does. If it is not a Built in Procedure,
     then it one of the below.

     Text/Menu/Script

     This tells the BBS that the name in the Filename field is one of these
     type of files and that it should display it to the user. Text files,
     Menu files or Script Files (not available yet) are to use this type.

     External Module

     This tells the BBS that the name in the Filename field is a program of
     some type and that it will need to execute it. You can run programs
     from the Command Table if the user chooses the Command.

     External BBS Module

     This also tells the BBS that the name in the Filename field is a
     program that it needs to execute BUT, there is a big difference in
     this type of file and the one above. This will tell the BBS to ALSO
     pass along certain information to the program. The User Editor is of
     this type of program and the location of the User information in
     memory is passed along to it. DO NOT use this type of field unless
     told to. If you do, it may have devastating results. Other modules
     will be written to specifically take advantage of this information and
     will tell you to set it up this way.

     Filename

     This is where you place the name of the Built in Procedure, the name
     of the Text File, Menu File or external program name. If no drive and
     path information is entered here, then the BBS will look in the
     MODULES folder for this file if it is a External Module or External
     BBS module or, if it is a text file, it will look in the TEXT folder
     for the file. If you want the BBS to look somewhere else for the file,
     the enter in the drive, path and filename of the file. Example:
     J:\MODULES\CHAT\CHAT.PRG or K:\MYSTUFF\JUNK.TXT.

     Reaction

     This is what will be sent to the user if he/she has Hotkeys enabled.
     You would enter something like 'Page Sysop!' if they selected the
     command to page the Sysop. Hotkeys just allows the user to make a
     selection without having to press return.





                                     - 23 -


     Access

     This will tell the BBS that user needs to have this Command Table
     Level (CTL) in order to use this command. This level is set in the
     User Editor under Security Levels for that user. If you assign New
     Users a CTL of 0 and you didn't want them to get into the File Areas,
     then you could enter a 1 here and New Users would not be able to
     access the File Areas. This works with ANY command.

     Parameters

     This will allow you to pass on parameters to programs that you execute
     from the Command Table. This is similar to passing parameters to a TTP
     file but, it allows you to pass them onto any type of program as long
     as the programs will accept them. The program should tell you what it
     needs. You can also place variable tags on this line. Please refer to
     the Variable Tags section for what is available. If a program took a
     parameter of the user's name for instance, you could put the variable
     tag {3} here and the user's name would be passed onto the program.

     Now you will notice some time fields. Remember, these times are to be
     entered in military time. They go from 00:00:00 to 23:59:59.

     Days of Week

     Down the left side of this screen, you will notice the days of the
     week. You can have a Command only on for certain days of the week if
     you wanted to and they would only work on that day. If the day is
     highlighted, then the Command is ON for that day.

     On At and Off At Times

     You will notice beside each day there is an On At and Off At time
     fields. This allows you to have that Command only on for certain times
     of the day. You can combine this with certain days of the week. Just
     enter the times you want this Command available. If you have the On At
     AND Off At times set at 00:00:00, then the command is considered
     ALWAYS ON. If you have some other time say, On At: 01:00:00 and Off
     At: 01:00:00, this would be the same as having that command turned
     OFF.

     You can have several commands with the same KEY entry and only have 1
     on at a time. For instance, you could have your Online Games only on
     Monday through Friday from 18:00:00 (6:00 pm) to 23:00:00 (11:00 pm)
     and the rest of the time, that KEY would be used for something else.

     When you come to a blank spot in the Command Tables, the times will
     default to On At: 00:00:00 Off At: 00:00:00 and all the days will be
     highlighted. This makes the default for that command ALWAYS ON on
     every day of the week. Since this is what you will normally have
     anyway, we just saved you the trouble of having to do it.









                                     - 24 -


     Daily Schedule

     You will notice a box with the words Daily Schedule in it. This option
     allows you to set all the days to ON and all the times to a certain
     time for each day of the week. Just click on this box with the mouse
     and you will see a dialog box pop up. In it you will see On At: and
     Off At: with the time field beside each one. You can enter your On
     Times and Off times here and select Exit. It will return to the
     Command setup screen and ALL the days will be highlighted and all the
     times set to what you entered. This is just a quick way to enter all
     the On and Off times. When you select this item and you only want to
     change the Off time, then you could TAB over to the Off time and
     change it and the On Time would remain set at what it was. the same
     goes for just setting the On time.

     Exit

     This will allow you to Exit the setup screen. When you do, you will be
     asked if you want to Save the Command Tables. Choose what you want to
     do. Even if you do not want to Save them, the changes you made will
     still be in memory so the next time you coma to the Command tables,
     your changes will still be there. This is one of the purposes of the
     Reload Command Tables. It allows you to reload them from disk if you
     have chosen Exit and do no want the changes in memory (start over in
     other words). Once you save the Command tables however, the changes
     are permanent until you change them again and save them. All changes
     will NOT be Saved to DISK until you tell it to when it ask you.

     Cancel

     This option allows you to also exit from the Command Tables setup
     screen but, choosing this option will tell the program to forget what
     you have done. The program will not ask you if you want to Save the
     Command Tables either. if you selected it by mistake, you will have to
     go back in and make your changes again. This is the ONLY command that
     will make the program FORGET what you have done. ALL others will save
     the info into memory.

     Change Tables

     This option will allow you to change to one of the other Command
     Tables. You will be presented with the same dialog box that you got
     when you chose the Edit Command Tables option. Choose which Command
     Table you want to go to. Using this option will also save the changes
     you made to memory.

     Find Key

     This will allow you to search the currently selected Command Table for
     a particular KEY (entered in the Key field). You can enter upper or
     lowercase letters.









                                     - 25 -


     Print Tables

     This option will allow you to print out your Command Tables. You will
     be presented with 4 options. This option will only print out the
     Commands for the currently selected Command Table. If you want the
     other Command Tables printed out, then select them using the Change
     Tables option and reselect this option.

     Print Commands Only

     This option will print out the top portion of the setup screen only.
     It will not print out the time schedule for that Command. It will
     print out 8 Commands per page.

     Print Commands With Schedule

     This option will print out all of the information in the setup screen
     including the time schedule. It will print out 4 Commands per page.

     Print Commands With Partial Schedule

     This option is much like the one above except, it will only print the
     days in the schedule that are turned on (highlighted). If you only had
     Saturday and Sunday turned on in a Command, then it would only print
     out those days and times. It will print out 4 Commands per page.

     Command Summary

     This option will present you with a dialog box that contains a summary
     of the Commands available in the currently selected Command Table. It
     will display 8 commands at a time. It will show you the Keystroke,
     Filename and Reaction of each command. Click on the arrows to page up
     or down through the Commands. If you click on a Filename field, the
     program will take you back to the setup screen and will display the
     Command you selected. This is a quick way to locate a Command or even
     a blank spot to put something in.
























                                     - 26 -


     PROTOCOLS

     This option will allow to edit the key that chooses the protocol and
     the filename of the external transfer program. Currently, the BBS uses
     it's own transfer program for everything except Ymodem-G and Zmodem.
     Ymodem-G is currently unavailable but will be added later on. You will
     be presented with 3 options.

     EDIT PROTOCOLS

     This will allow you to edit the Key required to choose the protocol
     and the filename of the program. You should have received a
     PROTOCOL.DAT file with your program. It should be in the DATA folder.
     There are 2 transfer programs called XFER.TTP (our own program) and
     XYZ.TTP. These files need to be placed in the MODULES folder. You can
     rename the files if you like keeping up with version numbers or
     whatever. Just make sure everything matches. XFER.TTP should be used
     for everything except Ymodem-G and Zmodem.

     You will be presented with a dialog box with the following options.

     Key

     This option allows you to assign a key to that particular protocol.

     Filename

     This is the filename of the external program. This must match with the
     name of the file in the MODULES folder.

     Next

     This will take you to the next available protocol. Selecting this
     option will save any changes you made to memory.

     Previous

     This will take you to the previous available protocol. Selecting this
     option will save any changes you made to memory.

     Cancel

     This option will allow you to exit without any of the changes being
     saved to memory.
















                                     - 27 -


     Exit

     This option will allow you to Exit the setup screen. The program will
     then ask you if you want to Save Protocol Data. Selecting NO will
     still leave the changes in memory. You can select the Reload Protocol
     Data option if you wish to have the data put back to the way it was.
     Once you Save it though, the changes are permanent until you change
     them again and Save the information.

     RELOAD PROTOCOL DATA

     This will allow you to reload the protocol information from disk. If
     you made some changes and decided you wanted to start over, then
     select this option.

     EXIT

     This will take you back to the Main Menu.










































                                     - 28 -


     MACROS

     Macros allow the user to enter in key sequences, characters, or
     whatever into a string which is saved to disk. When the user logs on
     and this file is found (located in the DATA folder), it will pull up
     the Macro data for that user. This will allow them to use this macro
     by pressing Control-A and then the number of the Macro. They do NOT
     hold down Control-A while pressing the number. If I stored my name in
     macro number 1, then anytime I wanted to put my name somewhere, all I
     would do is press Control-A and then the number 1 and my name would be
     inserted where the cursor is.

     You can allow up to 256 macros with up to 256 characters per macro per
     user. This is a little of an overkill though. Generally you would
     allow 10 macros with up to 20 characters per macro.

     You will be presented with 3 options.

     REFORMAT

     This will allow you to reformat/redefine your macros. When you choose
     this option, the program will ask you the number of macros to allow
     for each user and then how many characters to allow per macro.
     Selecting Exit with NO numbers in either dialog box that is presented
     will allow you to abort the operation. Once you have entered the
     information, the program will inform you that the MACROS.DAT file
     exist and ask if you want to overwrite it.

     DELETE

     This option will allow you to delete the MACROS.DAT file. You will be
     asked if you are sure you want to do this.

     EXIT

     This option will return you to the Main Menu.
























                                     - 29 -


     EVENTS

     The Event System in the BBS is a way to allow you to schedule programs
     to run at certain times of the day and certain days of the week. This
     allows you to run maintenance programs, network programs, etc., that
     must be ran at certain times. Some programs are designed to run in
     this fashion. The EVENT.DAT file is stored in the DATA folder.

     This will provide you with 6 options.

     EDIT EVENTS

     This will allow you to edit an existing Event's information. Below is
     the Event setup information.

     Filename

     This is where you place the drive, path and filename of the program to
     execute. There is no default location that the BBS will look for these
     files so, you must tell it where to find the file. If there is no
     information in this field, then the Event will not be ran.

     Parameters

     This is where you would place any parameters that must be passed onto
     the program. This is like passing parameters to a TTP program.

     Priority

     This is where you would tell the BBS what priority this Event has when
     it comes to someone being Online when it comes time to run this event.
     There are 5 priorities.

       0 - This will turn the Event off.

       1 - This is Low priority. This will tell the BBS to wait until a
           user has logged off of the BBS before running it. If the time
           limit for this event has expired (the current time is later than
           the off time), then the Event will not be ran. If you really
           want this Event to run, then allow enough time between the On
           and Off time so that the difference will be greater than the
           amount of time a user has per call or, set it to a higher
           priority.

       2 - This is Medium priority. This will tell the BBS too execute this
           program while the user is still online. It will warn the user
           ahead of time (set by the Warn Events Activating in xx Minutes
           on Settings page 2) that the event is going to take place and
           then when the time comes, it will tell them that it is executing
           the event. This would be okay for quick programs that need to be
           ran but, you don't want to kick the user offline in order to run
           it.








                                     - 30 -


       3 - This is High priority. This tells the BBS to run this program no
           matter what. It will warn the user that the event is executing
           at the On time and will reduce the user's amount of time left
           for that call by the appropriate amount. When there time is up,
           the BBS will hang up on them and then execute the event. There
           will be a 1 - 2 minute difference between the time the user gets
           kicked off and the time the event actually runs. It will NOT
           however, kick the Sysop off. Your time left online will start
           counting into the negative numbers.

       4 - This priority tell the BBS to run this Event after each call.
           When a user logs off (even the Sysop), the event will run.

       5 - This priority is the same as 4 except, it will not execute after
           a local call (you logon from the keyboard). It will only run if
           the user is on remotely.

     Modem Info

     This is used to send information to the modem before executing this
     Event. If you wanted the phone to be taken offhook while the Event ran
     so that nobody could call, then you would enter the appropriate
     command that would tell the modem to take the phone offhook. For a
     Hayes Compatible type modem, this would be ATH1. After the Event has
     executed and the BBS returns to the WaitCall screen, the modem will be
     reset and ready for a call.

     Days of Week and Time Fields

     You can tell the BBS that you want this Event to be ran at certain
     times of the day and certain days of the week. To activate the Event
     for that day, just highlight the day(s) you want it ran. To highlight
     the day, just click on it with the mouse using the left mouse button.

     Set up the time that you want the Event to execute by entering the
     time in the On At and Off At fields. The BBS will execute the program
     at that that time or before the Off At time.

     To turn it on ALL the time, then enter 00:00:00 in both the On At and
     Off At fields. This tell the BBS that you don't care when it get ran
     that day, you just want it to be ran. Normally you would enter in
     certain times. These times are in military time.

     To turn it off for that day, you can also enter in something like On
     At: 01:00:00 and Off At: 01:00:00. This is the same thing as
     deselecting the Day to turn it off.














                                     - 31 -


     Daily Schedule

     If you click on this box with the left mouse button, you will be
     presented with a dialog box that has a On At and Off At time field.
     This will let you configure the Event to be ran the same time every
     day. It will set ALL times to what you enter and highlight ALL the
     days. This is just a quick way of setting the times up. If you want to
     only change all the On At times, then you could select this option and
     only enter the new On At time and the Off At times will be left alone.
     This goes for only changing the Off At time also.

     Next

     This will take you to the Next available Event.

     Previous

     This will take you to the Previous Event.

     Exit

     This will allow you to Exit the editing of an event. You will be asked
     if you want to save your Event Data. Even if you do not save your
     Event Data, all changes are still in memory.

     REFORMAT EVENTS

     This will wipe out ALL Event data. You will be asked if you are sure
     before it does it.

     EXTEND EVENTS

     This option will allow you to add more Events to your Event Data file.
     If you have for instance, 3 Events and you want to add more, just
     select this option and enter the number of events you want to add. You
     can abort this by not entering any information and selecting Exit. You
     MUST use this option in order to add more Events.

     DELETE EVENT

     This option will allow you to Delete an Event. You will be asked which
     Event number to Delete and then asked if you are sure. When you Delete
     an Event, the others are pulled up to take it's place. In other words,
     if you delete Event number 2, then number 3 will become number 2 and
     number 4 will become number 3, and so on.

     RELOAD EVENT DATA

     This will allow you to reload the Event data from disk. If you change
     a lot of stuff and just want to start over and you haven't saved the
     Event data, then you can use this option.

     EXIT

     This will allow you to return to the Main Menu.





                                     - 32 -


     DRIVES

     DRIVES AND PATHS

       The "Drives & Paths" menu is where you tell the BBS how it should
     store its data.  We suggest leaving the path names the same, but you
     may change them to something you prefer.

       If you are going to use only one drive for each type of data, then
     simply only enter the one drive-letter in the appropriate field.  If
     you plan to use multiple drives for a data type then enter all of the
     drives with no spaces between them.  For example, if you would like to
     use drives C, D, and F for your data file, then enter "CDF" in that
     proper field.  (Do not include the quotes of course).  When the BBS
     sees this drive list (CDF) it will first check drive C for a file,
     then drive D, and lastly drive F.  You may rearrange the order of the
     drive list.  For example, if drive "F" was a RAMdisk you would want it
     checked before drives C & D, since a RAMdisk is so fast.

     The different types of data stored by the BBS are as follows:

     Data Files

     This is where files such as the userlog, mask information, and .LOG
     files are stored.

     Message Bases

     This is where all the Message Base and Email files are stored.

     File Areas

     This is where all the File Area folders and information are stored.

     Text Files

     This is where all text files are stored. These are file such as
     MAINMENU.TXT, LOGOFF.TXT, etc.

     Backups

     This is where all files that are backed up by the BBS are stored.

     Module Routines

     This is where external "modules" are stored. These are files such as
     ARC.TTP, LZH.TTP, XYZ.TTP, Event Modules, etc.

     Fmail/Fmessages

     This is where all Fmail and Fmessage files are stored. Fmail is just
     Email with a file attached and Fmessages are just messages with a file
     attached.

     Temporary Files

     This is where files such as Informer files are stored.



                                     - 33 -


     Main BBS Folder

     This is where all the folders and information above is stored. If you
     wanted ALL files associated with the BBS in the folder TRANS (We
     recommend it) then do not alter this field, otherwise change it to
     what you want.

     Exit

     After you have set up your drives & paths select the "Exit" button.
     The system editor will now create all of the folders for you.  If you
     have selected a lot of partitions this may take a little while. If you
     have already created the folders, then there will be no harm in it
     trying to create the folders again. This is just to insure that ALL
     folders have been created.

     After the folders have been created, the program will copy some of the
     files to their proper location if it finds them.

     Cancel

     This will allow you to Exit the setup screen without any changes being
     saved to memory. You will not be asked anything and will return to the
     Main Menu.




































                                     - 34 -


     USERLOG

     This option will allow you to Reformat your Userlog or change the size
     of it. You will be presented with 4 options. The USERS.DAT file is
     located in the DATA folder. You may want to back it up occasionally.

     REFORMAT USERLOG

     This option will allow you to zero out your ENTIRE Userlog. You WILL
     be asked if you are sure. It's a good way to piss off your users.

     INCREASE USERLOG

     This option will allow you to add more User slots to your USERS.DAT
     file.

     DECREASE USERLOG

     This option should be used with care. It will allow you to decrease
     the number of slots available in the USERS.DAT file. A very large
     number of user slots will slow the program down. If you find that you
     set the BBS up for too many users, then you can use this option to
     decrease it. There is a safety feature built in. The program will
     first search the USERS.DAT file starting at the end and working it's
     way back to the start. When it comes to a slot that has information in
     it, it will stop and tell you how many slots you can delete. Enter any
     number up to that point. The program will make a BACKUP copy of the
     USERS.DAT and USERS.IDX file. It will rename them to USERS.DA and
     USERS.ID. It will use these files to copy the information to the newly
     created USERS.DAT file and USERS.IDX file. If you change your mind,
     then you can delete the new files and rename the old files to their
     appropriate names. If a user has joined since you created the new file
     however and you do this, then their information will be lost.

     EXIT

     This option will return you to the Main Menu.


     REFORMAT MASK

     This option will allow you to Reformat your MASKS.DAT file which is
     located in the DATA folder. A Mask is a way to set up user information
     in a record so that you can apply all the information stored in the
     mask to the user. It is easier than having to enter the information
     into the user's record by hand each time. You just tell it what mask
     to apply and that's it. There are 100 mask available for you to use.
     There should already be a MASKS.DAT file in the DATA folder with the
     first couple of Mask defined and the last mask (number 100) defined.
     Number 100 is setup to apply to the Sysop or anyone you want to give
     this access to. 100 has everything maxed out. You set up a Mask in the
     User Editor.








                                     - 35 -


     CLEANUP

     This option allows you to set up the information for the Cleanup
     program. The Cleanup program is a program that you can run as an Event
     to do certain BBS maintenance functions. Questions with a triangle
     beside it can either be selected with the mouse or the information
     typed in. The Cleanup program is currently in the testing stages and
     is not available at this moment.

     Delete Email after ____ Days

     This will tell the program how long to keep Email before it is
     deleted. If you enter a zero here, the program will not delete any
     Email now matter how old it is.

     Delete Fmail after ____ Days

     This works the same as above except for Fmail messages. Fmail is just
     Email with a file attached. If you enter a zero here, the program will
     not delete any Fmail.

     Delete Fmail File Also ___

     This tells the program whether or not to delete the Fmail file when it
     deletes the Fmail message.

     Archive File Areas ___

     This tells the program whether or not you want it to compress files
     that are not already compressed. This goes hand in hand with the
     Auto-Compress selection in each File Area setup.

     Archive File Areas with (ARC/LZH) ___

     This allows you to select either ARC or LZH as the compression type.

     Backup Files in BACKUP.DAT ___

     This tells the program whether or not to backup the files that are
     listed in the BACKUP.DAT file.

     Delete Inactive Users after ___ Days

     This tells the program how long a user should be inactive before
     he/she is deleted from the User Log. Each user can be set up to be
     bypassed when this operation is performed. Refer to the User Editor
     section for more information. If you enter a 0 (zero) here, then no
     users will be deleted.












                                     - 36 -


     Keep TRANS.LOG for ___ Days

     This tell the program how long it should keep a backup of the
     TRANS.LOG file. If you enter a number greater than 0, then the program
     will backup that file using a number system to track it. For instance,
     if you wanted the TRANS.LOG file to be kept for 2 days, the program
     would copy the TRANS.LOG file to the BACKUP folder and name it
     TRANS1.LOG. It would then create a new TRANS.LOG file. On the second
     night, it would copy the file to the BACKUP folder and rename it to
     TRANS2.LOG and create another new TRANS.LOG file. The third night, it
     would delete TRANS1.LOG, rename TRANS2.LOG to TRANS1.LOG and copy
     TRANS.LOG to the BACKUP folder and rename it to TRANS2.LOG and create
     a new TRANS.LOG file.

     The higher the number, the more backups it will make before deleting
     the first file. This helps keep the TRANS.LOG file manageable and also
     provide you with a backup.

     Re-Run BBS Each Night ___

     This tells the BBS to RERUN itself each night so that memory can be
     cleared.

     Reboot Computer Each Night

     This will cause the computer to re-booted so that memory can be
     cleared even better. This helps keep junk from getting into memory
     and causing problems. You will need to make sure that you have the BBS
     program setup so that it will auto-boot after the computer re-boots.

     Keep DOWNLOAD.LOG for ___ Days

     This works the same as TRANS.LOG except it's for the DOWNLOAD.LOG

     Keep UPLOAD.LOG for ___ Days

     This works the same as TRANS.LOG except it is for the UPLOAD.LOG.

     Keep CLEANUP.LOG for ___ Days

     This works the same as TRANS.LOG except it is for the CLEANUP.LOG.



















                                     - 37 -


     EDIT SETTINGS

     This selection will take you to another menu/dialog box. This is
     called the Setting Pages menu and gives you the option of choosing
     pages 1 through 5. The settings control a lot of the BBS and are
     broken down into 5 pages.

     The next five screens are the general settings for your BBS.  These
     sections contain all of the normal questions you would expect from a
     BBS program, plus many that are unique to Transcendence.  The first
     three pages are all text fields, (with the exception of one) and the
     last two are ON/OFF settings.  The ON/OFF settings can be toggled by
     clicking on that field with your left mouse button.

     PAGE 1

     BBS Name

     This is the name of your BBS. This is used sometimes in the program.

     Sysop Password

     This is the password that will be needed if the user has Sysop Access.
     Whenever the Secondary Password is asked for, this is the password
     that needs to be entered.  The password is not case sensitive, but
     the BBS will disconnect the user if it is misspelled.

     System Password

     This is the password that is needed when you have "Private BBS"
     (explained later) turned On.

     Last Caller

     This contains the Handle of the last caller to the BBS.

     Last Run Date

      This is the date the BBS was last ran.

     Keep Last How Many Callers

     This is the number of how many callers the BBS will track as who's
     called the BBS. When the user selects the command of 'Who's Called'
     they will see this many callers.

     Password Echo Character

     This is the character that is echoed back to a user when a password is
     entered. You want it to be a character that is recognized by all
     computers. You may want to use something like a period or an asterisk.

     Do not use the plus '+' character, it will put most modems into
     command mode!






                                     - 38 -


     Idle Baud Rate

     This is the Baud Rate that the modem idles at. In other words, the
     Baud Rate at which the modem is set to between calls. Normally this
     would be the maximum baud rate of your modem. If you are using a high
     speed modem, then you may want to set this field to 19200.

     Min. Baud Rate

     This is the minimum Baud Rate that you will accept from a user. If you
     don't want 300 baud callers, then enter 1200 and so on.

     Max. Baud Rate

     This is the maximum Baud Rate you will accept. Normally this would be
     the maximum baud rate of your modem. If you are using a high speed
     modem, then you may want to set this field to 19200.

     Default Country

     When a user is asked for their Country, if they press return, this is
     what the BBS will default to.

     New User Mask

     This is the mask that will be applied to ALL New Users. A user is
     considered New if he/she does not have an account on the BBS and
     answers Yes to the question of whether or not they wish to have an
     account on the BBS. The mask system is explained in detail in the
     User-Editor section.

     Guest User Mask

     This is the mask that will be applied to Guest users. A user is
     considered a Guest when he/she does not have an account on the BBS
     and answers No to the question of whether or not they want an account
     on the BBS or if they type "Guest" or "Visitor" for their handle.

     Verified User Mask

     When using the Auto-Verifier, this mask will be applied if the user
     passes the auto-verification. Auto-verify is explained later.

     Idle Timeout

     This is the amount of time that elapses when no interaction to the BBS
     has taken place by a user. After this amount of inactivity has taken
     place, the BBS will automatically log the user off. He/She will be
     warned 30 seconds before hand.  This number is in seconds, and can
     range from 30 to 255.










                                     - 39 -


     PAGE 2

     Calls Today

     This just displays the number of calls the BBS has received today.

     Calls Total

     This is the total amount of calls the BBS has received since it was
     created. If you were previously running a BBS you may want to put the
     number of calls from that BBS program, here. The number of calls will
     start at that point. Otherwise leave it blank.

     Node Number

     This is for Networking, for now leave it at its default.

     Node Name

     This is for Networking, for now leave it at its default.

     Node City

     This is for Networking, for now leave it at its default.

     Send Feedback to User #

     This will allow you to redirect Feedback to any valid user. Normally
     this is set to you number but, if you wanted to go on vacation and had
     a remote sysop handling things, you could tell it to redirect all
     feedback to that user number. Before changing this number, be sure
     the user number you change it to does exist!

     Local Dial

     This is the prefix for your modem to dial a local number, normally
     this would be "ATDT" (Tone) or "ATDP" (Pulse).

     Long Distance Dial

     This is the prefix for your modem to dial long distance. Normally this
     would be "ATDT1" (Tone) or "ATDP1" (Pulse).

     Area Codes

     These are the area codes that you can reach locally. This is how the
     BBS can tell if a caller is local or long distance.













                                     - 40 -


     Chat On

     This tell the BBS what time to start allowing the users to page you.

     Chat Off

     This tell the BBS what time to stop allowing the users to page you.

     Initialize Modem Every xx Minutes

     This tells the BBS how often to send the modem initialization string
     to the modem between calls. The BBS will resend it this many minute(s)
     later. Enter '0' if you do not want this option. 255 is the maximum
     input for this option.

     Warn Events Activating in xx Minutes

     This will tell the BBS when to start warning a user that an event is
     about to take place. If a user has 60 minutes online, and their time
     limit is shortened due to an upcoming event, the BBS will tell them.
     This is only if their time left is greater than this figure. You may
     enter values up to 255 in this field.

     Upload File Area

     This tells the BBS what file area to send ALL files to. This was
     designed to allow the Sysop to have all files sent to one area and
     then decide where to put them when validated. This setting works hand
     in hand with 'Uploads go to Sysop File Area' on page 5. One will not
     work without the other. This number (File Area number) must be higher
     than 0 if this function is going to be used.  Select '0' if you do not
     want to use this function or you can turn it off on Page 5.

     BBS Operation Hours

     This is the time that the BBS will be active. Click on the words "BBS
     Operation Hours" and a dialog box will appear. If your BBS will only
     be up certain hours of the day, then enter the hours in these fields.
     During "ON" times (When your BBS should be up) the BBS will send the
     normal string to your modem, so the modem will answer the phone.
     During "OFF" times, the BBS will send a string to the modem causing it
     not to answer the phone.


















                                     - 41 -


     PAGE 3

     Lock Baud Rate

     This tell the BBS to lock the Baud settings in the computer to a
     certain baud rate. This is only needed if you have a high speed modem
     or MNP (Data compression) modem.  When you use this the BBS will
     always "talk" to the modem at this baud rate, although the users can
     still call at other baud rates. This is explained in more detail in
     the section on configuring your modem.

     Auto-Informing Messages to User #

     This works the same as Feedback goes to User #. Any Informer messages
     goes to this user. Normally this would be the Sysop (User #1). The
     Auto Informer is explained later.

     Default Window Size

     This is the default size of the window when Transcendence is booted up.

     The next 2 items are templates. This will allow you to set up how you
     want the user to enter in the State or Phone Number. There are 4 types
     of characters the BBS will recognize in this mask and act on. The BBS
     used to these 2 items automatically but, due to European information
     being in a different format, I had to change it and decided to leave
     it up to the Sysop as to how he wanted it.

       X (uppercase X) will tell the BBS to convert the data the user
     enters to uppercase. The user will not have to press the Shift key to
     do this. This character will also tell the BBS to accept ANY printable
     character as input.

       x (lowercase x) will tell the BBS not to convert the data to
     uppercase if the user does not have the Shift key pressed. If they do,
     then the BBS will accept it as an uppercase though. This will also
     tell the BBS to accept ANY printable character as input.

       # (number sign) will tell the BBS to only allow numbers for this
     position in the template.

       | (the BAR character) will tell the BBS to wait for the user to hit
     RETURN before processing this data. If this is left off, then when the
     user reaches the maximum number of characters that can be entered, the
     BBS will automatically process the data as if the user hit RETURN.

       Any other character in the template will be automatically inserted
     by the BBS as the user enters the data. For Example, the Phone Number
     template was (###) ###-####|. The BBS would then automatically enter
     the '(', ')',  ' ' (space) and '-' as the user typed in his Phone
     Number.









                                     - 42 -


     State Mask

     This is where you set up the template for the State information. The
     way it was set up in the BBS before was XX|. This would tell the
     program to allow 2 characters to be entered and convert them to
     uppercase and wait for the user to hit RETURN. You can enter up to 20
     characters in this field. You can use all 20 for data and not use the
     '|' or you can use 19 characters for data and use the '|'.

     Phone Mask

     This is where you set up the template for the Phone Number. The way it
     was set up in the BBS before was (###) ###-####|. This would tell the
     BBS to allow the user to enter in 10 numbers and automatically insert
     the other characters as the user type in his Phone Number. You can
     only use up to 14 characters for data. The last space is only to be
     used by the '|' character. If you do use it for something else, it
     will be ignored.

     Time Left for Online Game

     This allows you to set the amount of time (in minutes) that is
     required for a user to have left Online before they can play an Online
     Game. For example, if you set it to 15 minutes, then the user will
     have to have 15 or more minutes left online for that call in order to
     play the game. This will help stop a user waiting to the last minute
     to go into an Online Game and spending more time than he is allowed
     online.

     PAGE 4

       The next two pages are "toggle" fields.  Using your left mouse
     button you can toggle them on or off.  If the field is highlighted,
     then it is ON.

     RTS/CTS

     This tell the BBS to set RTS/CTS On/Off. This is only used for high
     speed modems or MNP modems.  Most versions of TOS have a problem with
     RTS/CTS and require a patch to use it.  Most of the patch programs
     can be found on the Transcendence Support BBS. RTS/CTS prevents remote
     users from getting too much text at once, or loosing text, when they
     connect to a high speed modem. This is known as hardware handshaking.

     Allow Remote Sysops

     If this is off the BBS will not allow a remote user to get into the
     Sysop Mode, even if they have access. It is simply a precautionary
     measure.











                                     - 43 -


     Screen Saver

     This tell the BBS to activate it's built in screen saver. The screen
     saver will toggle between a black screen and a normal screen if you
     are using a color monitor. If using a monochrome monitor, it will just
     toggle between black/white and white/black. The screen saver is a
     simple one and there are better ones already available that you may
     want to use.

     Allow Handles

     This tells the BBS whether or not to allow handles. If Off, the
     user's handle will be the same as their real name.

     Show VT52 Codes

     If this is turned on the BBS will display VT52 codes (Escape
     sequences) on the local end. If it is off you will see the actual ESC
     sequences, and won't see the color changes, text effects, etc.

     Snoop Mode

     This tells the BBS whether or not to have Snoop Mode default to On or
     Off when it is booted up. When snoop mode is on the sysop can see what
     a user is doing while online. If snoop mode is off, then the sysop can
     not see anything the user is doing. Having snoop mode off can increase
     the modem output slightly. This can also be toggled on/off with a
     function key.

     Printer Echo

     This tells the BBS to echo everything to the printer. You can use a
     lot of paper this way. If you want to generate a lot of paper to
     recycle, then this is for you. It just logs everything that is done
     by all users to the printer. This can also be toggled on or off with
     a function key.

     Disk Log

     This tells the BBS to send all Log information to TRANS.LOG in the
     DATA folder.

     Printer Log

     This tells the BBS to send all Log information to the printer.

     Fido

     This tells the BBS that you are Using Fido (BinkleyTerm). The BBS will
     look for SPAWNBBS.BAT (Created by Binkley), and react according to its
     contents. After the call is over the BBS attempts to run FIDOMAIL.BAT,
     which should have Binkleyterm's filename in it.








                                     - 44 -


     Local Security

     This tell the BBS that anytime the BBS is accessed from the keyboard,
     that it should ask for the Local Security Password. This is to help
     prevent those that come over to your place and decide they want to
     get at some information. This applies to access to the BBS, Sysop
     Functions (Dos commands) and the System Editor. If you implement this
     feature, and forget what the password is you can not run the System
     Editor, or get into your own BBS (Other than normal logon). It is very
     important you use this feature with caution.

     Term At logon

     This tell the BBS to ask for the terminal type each time a user logs
     on. If this option is off the BBS will allow the user to set up
     his/her terminal preference in their settings. The system will default
     to whatever is in the MENUS0 folder (normally ASCII text files) until
     the user logs on if this option if off.

     Hard Drive

     This tell the BBS that you are using a HD for the BBS. If this is
     turned off (Please, not a floppy based BBS!!!) the BBS will ask you
     to insert your data disk(s) after it reads the TRANS.DAT file. This
     is so (People have actually done this!?!) someone can run a BBS from
     a floppy, and swap the "Boot" disk with the "BBS" disk. Hopefully you
     will never experience this feature. You cannot run a good BBS from
     floppy.

     New User Email

     This will force a New User into Email when they apply for an account
     on the BBS.  The Email will be sent to the user setup to receive
     Feedback on Settings Page #2. The BBS will look for a file called
     NEWEMAIL.TXT and display it just before it puts the user in the editor
     so you can explain what is about to happen.

     Warn Low Space

     This tell the BBS to warn you when you are getting low on disk space.
     Whenever a partition has less than 500k free, you will get a warning
     when you log on.

     Printer Bells

     This tells the BBS to ring the printer bell also when it rings the
     system bell. This is handy if you have your monitor off and the
     system bell is sounded. You will need to have your printer on of
     course. Not having the printer on will cause the BBS to lock up until
     you turn it on. Some printers do not have speakers, refer to your
     printer manual to see if yours does.









                                     - 45 -


     Post? During QuickScan

     This will tell the BBS to ask the user if he/she wishes to post on
     that base during a QuickScan. If the user has QuickScan Message Bases
     turned on and comes to the end of the new messages, then the BBS will
     ask them if they wish to post on that base before it proceeds to the
     next base. If the user has replied to a message, then it will not ask
     them if they wish to post.

     Acknowledge Local Call

     If this is turned off the BBS will ignore local logons. The logon will
     not update the caller numbers, or be reported in the "WHO'S CALLED"
     list.

     Settings, New User

     This will force the new users into the Settings menu. This is where
     they set a lot of their defaults that is to be used by the BBS while
     they are online.

     Color Toggling

     This will tell the BBS to cycle through the colors. This is another
     form of a "screen saver," and it may be used in color or monochrome.

     Ring Back Local

     Ringback is a feature that lets the BBS call users back. If this is on
     the BBS will be able to call users back, if their area code is in your
     AREA CODE LIST (Settings Page #2). Ringback was designed mainly for
     users getting bad line noise, or are on "measured service" lines. When
     making a ringback call the BBS uses the "Data Phone Number" of the
     user, that is the second phone number it asks them for.


























                                     - 46 -


     PAGE 5

     Ringback Long Distance

     This is a ringback feature for long distance callers. Under normal
     circumstances you would want this feature off, unless you want to
     incur the expense of calling long distance users back. A long
     distance user is someone who's area code is not in your area code
     list (Settings Page #2).

     Auto Verify Local

     The Auto-Verify feature is used to verify a new users phone number.
     When a new user logs on, and is in your area code list, (Settings
     Page #2) the BBS will display a text file explaining what the
     auto-verify is, and then it will call them back and expect their
     modem to answer the call. The BBS will make three attempts to call
     them. If it succeeds, it will ask them their name & password, if it is
     correct they will have the "Auto-Verify Mask" applied to them
     instantly. This can ensure you that users give you a good phone
     number, and bypass you having to manually call them for verification.

     Auto Verify Long Distance

     This is the long distance equivalent of the above feature. Normally
     you would not want this feature on, since it would really rack up
     the phone bill.

     Uploads go to Sysop File Area

     This will tell the BBS that all uploads should go to the File Area
     defined here. This goes hand in hand with the corresponding question
     on page 2.

     Visual Alerts

     This will cause the screen to flash anytime the system bell is rang.
     This is to help the hearing impaired and those that may have the
     volume on their monitor turned down.

     Inform New Logon

     This tells the BBS to inform the user, set in Auto-Informer Messages
     to User # (Settings page 3) that a new user has logged on. When the
     user defined to receive informer-messages (Normally the Sysop) logs
     on they will be notified that a new user has logged on. The BBS will
     display some of their information, and allow the Sysop to preform
     routine maintenance right there. See the section on
     "The Auto Informer" for further information.











                                     - 47 -


     See Passwords Locally

     This tells the BBS whether or not to allow passwords to be seen
     locally. When this is off the Sysop (Or anyone else local) will see
     the "password echo" characters, instead of what the user is actually
     typing. Otherwise anyone local could see the password as the user
     types it.

     Inform of Bad User Logon

     This works the same as Inform New Logon except it informs you that a
     user that has been flagged as Bad, has logged on.

     Questor LZH Mode

     This is no longer used.

     Private BBS

     This tell the BBS not to allow anyone onto the BBS unless they know
     the System Password (Settings Page #1). There may be times in which
     you only want to have certain users be able to logon.

     BBS Answers Phone

     This tells the BBS that your modems "Auto-Answer" feature is turned
     off, and that the BBS should send an Answer command to your modem
     when it detects the phone ringing. This is explained in more detail
     in the section on setting up your modem.































                                     - 48 -


     MISC.

     VIEW SETTINGS

     This option will allow you to page through the settings showing you
     what you have selected. It will also show you the Message Base info
     and File Area info. Data CANNOT be edited while viewing your settings.

     SET COLORS

     This option will allow you to set up the colors the BBS will default
     to when ran. To increase the numbers, just click on the + field and
     to decrease the numbers, click on the - field. If you click and hold
     on one of the fields, the system will continue to increase or decrease
     the numbers. The colors will change as you change the numbers.

     BAUD RATE EDITOR

     This option will allow you to setup what baud rates are allowed at
     what times during the day. This will allow you to lock out certain
     baud rates during peak hours or whatever.







































                                     - 49 -


                       Chapter 2: Built-in BBS Procedures

         The BBS Built-in Procedures are commands that you allow the user
     to have access to. They can have their own KEY, set at certain access
     levels, turned on and off, turned on and off on certain days and at
     certain times, access text files, access external programs and much
     more. You activate and setup these commands via the Command Tables
     section in the System Editor. There is four sections of commands.
     These are, General, Main Menu,   Message Menu and File Menu. Below is
     what each command will do.

     GENERAL

     These commands can be used in the Main Menu, Message Menu, File Menu
     or the Menu Processor (menus).

     CALLSYS

     Allows the user to PAGE the Sysop.

     CONTLIST

     Allows the user to toggle Continuous Scroll On/Off for the file
     listings.

     EMAIL

     Allows the user to access the Email section.

     FEEDBACK

     Allows the user to Leave Feedback. This will cause the user to enter
     the Email section but, the program automatically sends the message to
     the user that has been defined in the 'Leave Feedback to User #' field
     in the System Editor.

     FILE_xxx

     This command allows you to access the File Area # (xxx) from within a
     MENU file.

        Example...

        1 p FILE_1  * Will send the user to File Area #1.

     GOODBYE

     Allows the user to log off of the BBS.












                                     - 50 -


     MACROS

     Allows the user to access the Macros section to define their Macros.

     MAIL_xxx

     This will allow you to send Email from within a MENU file to the User#
     (xxx). This is good for adding a logoff choice to send Email to the
     Sysop, Co-Sysop, etc. before the user logs off. You can also have
     several feedback choices from the Main Menu.

         Example...

         1 p MAIL_1  * Will send the user to Email and select User #1 as
                       the recipient.


     MARKBASE

     Allows the user to Mark which Message Bases he/she wishes to take part
     in.

     MSG_xxx

     This command allows you to access the Message Base # (xxx) from within
     a MENU file.

        Example...

        1 p MSG_1   * Will send the user to Message Base #1.

     OFF

     Allows the user to use the OFF command instead of goodbye. This is a
     quicker method of logging off. This will also display the OFF.TXT file
     instead of the LOGOFF.TXT file.

     OFFNOT

     Allows the user to abort logoff in the menu processor.

        Example...

        MENU
        Selection:
        2
        1 p MAIL_1
        2 p OFFNOT
        [1] Send Mail to Sysop
        [2] Abort Logoff










                                     - 51 -


     ONLINE

     Allows the user to access the Online Games section.

     OTHERBBS

     Allows the user to access the Built-in BBS Listing.

     PARMEDIT

     Allows the user to edit their parameters. The user (unless he is a new
     user) will not be able to change their Name or Handle. All other items
     can be changed. The user will have to request this to be done by you
     (the Sysop). This was added so that the user could not change his Name
     or Handle and re-enter an online game as someone else.

     RINGBACK

     Allows the user to request the RINGBACK feature.

     SCANEDIT

     Allows the user to mark which File Area he wishes to be active for
     things such as Searches, Scan for New Files, etc.

     SETTINGS

     Allows the user to adjust their settings. When this command is used,
     the BBS will display the EDITUSET.TXT file.

     SYSOP

     Allows the user to access the Sysop/DOS mode.

     TERMINAL

     Allows the user to set his/her terminal(VT52, ASCII, etc.) type.

     UEDITOR

     Allows the user to access the User Editor.

     USERLIST

     Allows the user to get a listing of the current users of the BBS.

     USERMES

     Allows the user to send a message that each caller will see as part of
     the logon sequence.

     USTATS

     This is another form of PARMEDIT. It only allows the user to change
     his Password (at the moment).

     VIEWCALL

     Allows the user to view the Who's Called Listing.

                                     - 52 -


     MAIN MENU

     These commands can only be used for the Main Menu.

     FILES

     Allows the user to gain access to the File Areas.

     F_SCAN

     Allows the user to scan the File Areas for new files. When using this
     command, the user will be returned to the Main Menu after the scan for
     New Files is completed.

     JUMPBASE

     Allows the user to Jump to another Message Base.

     MESBASE

     Allows the user to choose from the currently available Message Base to
     go to.

     Q_SCAN

     Allows the user to QuickScan the Message Bases for new messages.

     ZIPSCAN   (Currently inactive)

     Allows the user to collect all of the new messages and have them
     either ARCd, LZHd, or sent as ASCII. He then can download these
     messages so he can read them offline. A QuickMail compatible version
     of this command is in the works. It may also end up as a separate
     program.


























                                     - 53 -


     MESSAGE MENU

     These commands can only be used for the Message Menu.

     BASEINFO

     Allows the user to get information about the current Message Base.

     CHECKM

     Allows the user to check for message [T]o the user [F]rom the user or
     [B]oth.

     ENTERMSG

     Allows the user to enter a message.

     EXITMSG

     Allows the user to Exit the Message Base.

     MARKREAD

     Allows the user to read the message he previously marked for reading.

     MTOPIC

     Allows the user to view/change the Message Base Topic.

     NEW_MSG

     Allows the user to read new messages in the current Message Base.

     NEXTBASE

     Allows the user to move to the next available Message Base without a
     listing of available Message bases.

     OTHERMSG

     Allows the user to go to another Message Base and provides a listing
     of the currently available Message bases.

     PREVBASE

     Allows the user to move to the previous available Message Base without
     a listing of available Message Bases.

     READBACK

     Allows the user to read messages in reverse order.

     READFORW

     Allows the user to read messages in foward order.





                                     - 54 -


     READMSG#

     Allows the user to start reading messages at a certain number.

     SEARCHM

     Allows the user to search the contents of messages for certain words, etc.

     SETHIGH

     Allows the user to set his/her High Message Counter.

















































                                     - 55 -


     FILE MENU

     These commands can only be used for the File Menu.

     ARCUTILS

     Allows the user to go to the ARC/LZH DL Utilities.

     BTCHSEND

     Allows the user to start downloading the files that have been marked for batch download.

     CATALOG

     Allows the user to get a Catalog (short) listing of available files in
     the current File Area.

     DOWNLOAD

     Allows the user to enter the number/name of a file(s) to download.

     EXITFILS

     Allows the user to exit the File Area.

     FILOCATE

     Allows the user to do a Global search for a filename.

     FSYSOP

     Allows the user to access the File Maintenance section.

     LISTING

     Allows the user to get a Full Listing of the available files.

     MARKFILE

     Allows the user to Mark a file(s) for download.

     NEWFILES

     Allows the user to get a listing of all new files in all available
     File Areas. When using this command, the user will be left at the last
     File Area that was scanned.

     NEXTSIG

     Allows the user to move to the next available File Area without a
     listing of available File Areas.









                                     - 56 -


     OTHERS

     Allows the user to choose from the list of available File Areas to
     move to.

     PREVSIG

     Allows the user to move to the previous available File Area without a
     listing of available File Areas.

     READFILE

     Allows the user to enter the name/number of a file to read.















































                                     - 57 -


     SEARCH

     Allows the user to globally search the contents of a file for a
     particular word, letter, etc.

     SETLIST

     Allows the user to update his New Files Scan Date to the current Date
     so that ALL the files will not appear as New Files to him.

     SINCEDTE

     Allows the user to globally search for files uploaded since a certain
     date.

     UPLOAD

     Allows the user to upload a file to the current File Area.

     VIEWMARK

     Allows the user to view the file that have been marked for batch
     download.

     WIDELIST

     Allows the user to get a WIDE listing of all available files.

































                                     - 58 -


                         Chapter 3: Transfer Protocols

         Transcendence uses external programs to do it's file transfers.
     Currently, there are two different programs to do your transfer with.

         The first program is 'XFER.TTP'. This program is included with the
     BBS program. It includes Xmodem Checksum, Xmodem CRC, Xmodem 1K,
     Ymodem Batch and Fmodem Batch.

         The second program is XYZ.TTP from Alan Hamilton 'Starfall
     Software'. This program is available on most BBS systems including my
     BBS. I do not have the rights to distribute the program with the BBS,
     therefore it cannot be included with the package. You should use
     version 2.01 or higher of XYZ.TTP. Any version lower than 2.01 will
     not work correctly with the program. This program is Shareware so if
     you use it, please register it. It is well worth the small amount of
     money he is asking for.

         Both of these programs should go in your MODULES folder. Hopefully
     in the future, I will have ALL transfer protocols in one single
     program. Ymodem-G is being worked on.

         Refer to Chapter 1 for instructions on setting up these protocols.





































                                     - 59 -


                       Chapter 4: Personalizing Your BBS

       This chapter deals with personalizing your BBS to the way you want
     it. The Menu Processor, Data Files and Text Files are one of the major
     ways you can do this. Through the use of these files, you can make
     your BBS look TOTALLY different from the other guy's. Also, the use of
     Variable Tags in these files can be used to display variables that are
     stored by the BBS internally or Sysop definable variable Tags.


     MENU PROCESSOR

       The Menu Processor allows you to design Menus to control quite a few
     things. One of the major uses is for Online Games. It does however
     have a lot more uses than that as the majority of the BBS Procedures
     can be used from within a Menu. This opens up a wide range of
     possibilities. Through the Menu Processor, you can have the BBS
     execute programs, display Text Files, use the BBS Procedures, go to
     certain File Areas or Message Bases, send Email to certain people,
     organize your file Area and Message Bases into categories, and so on.

     Setting up a MENU

     A MENU must be laid out in a certain way. The first three lines of a
     menu describe how the menu should work.

     The first line is the OPTIONS line. It tells the BBS is it's a MENU,
     if the user can ABORT it, what level a user must be to access it, and
     many other things.

     The second line is the PROMPT line. It is the prompt that the user
     will see after the menu has been displayed.

     The third line is the number of menu selections available in that
     menu.

     After the first 3 lines is your Selection List. This list can be as
     long as you specified in line 3. After the list is complete, you will
     then place the text that the user will actually see. The text portion
     can be anyway you like. You can include VT52 codes, ANSI codes, put
     text in any location, etc. Whatever you want.



















                                     - 60 -


     OPTIONS LINE

     The OPTION line MUST start with the words MENU or TEXT. TEXT files
     will be explained later. After that, you can place any of the other
     options in any order you want.

     Available Options

     MENU

     This tells the BBS that this file is a MENU file.

     TEXT

     This tells the BBS that this file is a TEXT file. This is not really
     needed for a Text File but, if you plan to use the NOABORT option or
     others explained below, then you will have to place the word TEXT as
     the FIRST option for a plain text file.

     NOABORT

     This tells the BBS to not allow the user to abort the output of this
     file with a ^C (Control-C).

     NOPAUSE

     This tells the BBS to not allow the user to pause the output of this
     file with ^S (Control-S).

     LEVEL_xxx

     This tells the BBS that the user must have a level of at least xxx to
     see or use this menu. xxx can be any number from 0 to 255.

     AGE_xx

     This tell the BBS that the user must be at least xx years old to see
     or use this menu.

     MONLY

     This tells the BBS to only allow Male users to see or use this menu.

     FONLY

     This tell the BBS to only allow Female users to see or use this menu.














                                     - 61 -


     FREE

     This tells the BBS to put the user in Free Time mode. This means that
     the user will not be charged online time as long as they are in this
     menu. This was designed so that you can use alternate Chat programs
     and the user not get charged any time while in chat. This causes the
     BBS to act as if the built in Chat mode was used as it doesn't charge
     the user any time.

     Examples:

     MENU NOABORT LEVEL_100

     This would tell the BBS to only allow users with a Menu Access Level
     of 100 to see or use this menu and they could not abort the output of
     the menu with ^C (Control-C).

     MENU AGE_18 NOPAUSE FONLY

     This would tell the BBS to only allow users that are 18 or older and
     Female to see or use this menu. They cannot pause this menu with ^S
     (Control-S).

     Selections Line

     The selection line is anything you want it to be. This is the prompt
     that will be displayed to the user to make their selection. Usually it
     would be something like "Make your Selection: ". This line can be any
     length from 1-80 characters, so you can center it or whatever.

     Menu Selections

     You may have up to 256 selections for each Menu file. The number of
     selections will be reflected in Line #3 of the Menu file. The forth
     line starts your selections list. This will tell the BBS how to handle
     that selection. You can have four types of selections from a menu. The
     syntax for the selection looks like this:

     key type filename Return (Y or N) Special

     KEY

     The key field is the keypress required from the user to use that
     selection.

     You can also use the DEFAULT command in the key field. This
     will tell the BBS that this is the action to take if a key is selected
     that is not in the selections. Normally this would be combined with
     the Exit command explained later.

     Another option in the Key field is the '@' key. This will tell the BBS
     that if the user presses RETURN, to do this selection. Since it is
     hard to enter the RETURN character in a file, the '@' symbol is used
     as a replacement.






                                     - 62 -


     TYPE

     There are four different Types of selections you can use. Below is a
     description of each type.

     P or B

     Using one of these characters will tell the BBS that this selection is
     used to perform a COMMAND normally performed by in the COMMAND TABLES
     (built in Procedures). Refer to the Built In Procedures section for
     explanations of these Commands. With this, you could have menu
     options to Page the Sysop, Leave Feedback to a user, or just about
     anything. You would place the name of the Command in the Filename part
     of the selection.

     C, E or X

     Using one of these characters will tell the BBS that this selection is
     to be used to execute an external program. An example would be
     running an separate Split-Screen chat program. The drive, path and
     filename of the program to execute is placed in the Filename field of
     the selection. if only the filename is given, then the BBS will look
     in the MODULES folder for the file. You would place any parameters
     that need to be passed onto the program in the Special field of the
     selection.

     D

     Using this character will tell the BBS to execute an External BBS
     Module. This is an external program that is specifically designed to
     receive the buffer address information passed onto it by the BBS. DO
     NOT use this Type option unless told to. You should get instructions
     with the program explaining how to set it up. The programs will use
     special information passed onto it and if you do set it up properly,
     the program or BBS will probably crash or do nasty things to the
     information located in the buffers.

     The buffers holds information about the user, system, currently
     defined variables, etc. If the location of this information is not
     passed on correctly, it can have ill effects.

     T or M

     Using one of these characters will tell the BBS that this selection is
     to be used to display a Text file or a Menu file. You can have Menus
     within Menus. The complete path and filename of the file to display is
     to be placed in the filename field of the selection. If you do not
     include a path, the BBS will look inside the MENUSx folder for the
     file. You can go to 25 levels of Menus (Menus within Menus). You will
     get an error message if you go over that limit.










                                     - 63 -


     O or G

     Using one of these characters will tell the BBS that this selection is
     to be used to execute an Online Game. The filename is the complete
     path and filename of the file to execute. If no path is given, then
     the BBS will look in the MODULES folder for the file. The Return field
     is used for the type of data file to write. This can be TURBO, FOREM,
     TRANS, OTHER or STAR. The Special field is used to pass on parameters
     to the program. Usually something like LOCAL to tell the program that
     the user is a LOCAL logon (sysop). You can also use a number (1,2,etc)
     in the filename field. This will tell the BBS to look in the DATA
     folder for the ONLINExx.DAT file. 'xx' represents the number you
     placed in the filename field. This is the preferred method of setting
     up an Online Game and will be discussed in more depth later.

     Exit

     This option is placed in the Type field and is used to exit a menu.
     This must be here in order for a user to be able to exit the menu.

     Exitall

     This option is also placed in the Type field and is used to exit the
     menu but, it will exit all the way back to the Main BBS Menu. This
     will give the user the choice to abort out of all the menus in one
     shot without having to select Exit on each menu they have gone into.
     This is mainly used on menus that are two or more levels deep.

     FILENAME

     This is where you place the complete path and/or filename of a program
     to execute, display, the name of a Command (Built in Procedure) or,
     the number of the ONLINEx.DAT file to look for in the DATA folder.

     RETURN

     This is where you tell the BBS to tell the user to Press Return after
     the selection they make is completed. For instance, if they choose an
     option that will display a text file, the BBS will prompt the user to
     Press Return before coming back to the menu and re-displaying the
     menu. By placing a Y in this field (or leaving it blank) will tell the
     BBS to prompt the user. If a N is placed here, the BBS will not prompt
     the user to press Return. This field can also be used for other things
     as mentioned above.
















                                     - 64 -


     SPECIAL

     The Special field is used to enter in the parameter that you want
     passed onto a program. This is similar to passing parameters to a TTP
     file but, a lot of other types of files also accept parameters.
     Usually, the programs will tell you what parameters it wants or
     expects.

     Some Examples

     Below is some examples of a menu.

     MENU                                <---|
     Selections [Press return to exit]:      |
     5                                       |
     A t C:\BBS\TEXT\LOVE.TXT                |   Used by the BBS
     B t C:\BBS\TEXT\MONEY.TXT               |
     C t C:\BBS\TEXT\CARS.TXT                |
     D t C:\BBS\TEXT\BBS.TXT                 |
     DEFAULT EXIT                        <----
     {1}Example Data Base                           <---|
                                                        |
     [A] Meet the women of your dreams                  |  Displayed to
     [B] How to make $1,000,000.00 in just 2 weeks      |  the user.
     [C] Best buys on cars in 1992                      |
     [D] National BBS Listing (Updated 1/20/1990)   <---|

     That is all there is to it. The user sees the part marked as Displayed
     to the User and the Selection Prompt (line 2). If they choose A, B, C
     or D, then the proper file will be displayed. If they press any other
     key (even Return), then the BBS will exit that menu. You will also
     notice that the RETURN field was not used. Not placing an N there, the
     BBS will default to displaying the Press Return prompt.


     MENU NOABORT LEVEL_50
     What's it gonna be (Q=Exit)?
     4
     1 c C:\BBS\SPITSCRN.PRG N
     2 c D:\BBS\CHITCHAT.PRG N
     3 p CALLSYS N
     Q exit
     {1}Chat modes:

     [1] Split Screen Chat (Vt52)
     [2] Split Screen Chat (Vt100/ANSI)
     [3] Normal Chat
     [Q] Exit Menu

     In the above example, you will notice some more options on the Options
     line. This is how they are spaced out. The line translates to 'This is
     a Menu file and do NOT allow the user to abort the displaying of the
     menu and they must have a Menu Level of 50 or higher in order to use
     it".






                                     - 65 -


     The return field was used to tell the BBS not to display the Press
     Return prompt after the processing of the selection. The first 2 lines
     of the selections told the BBS to execute external programs and the
     third line told the BBS to use the Built in Procedure (Command) called
     CALLSYS.

     The Menu also has the Exit command in a selection and they have to
     select Q in order to exit the Menu. Any other key in this instance
     will just re-display the Menu.

     Other Information

     You will notice in each example a '{1}' in there. This is the variable
     tag that tells the BBS to clear the screen. Variable tags can be used
     anywhere in the menu (or a text file) except in the Key, Type,
     Filename and Return fields. Everywhere else is free game. You can even
     use them as parameters to a program. The BBS will detect a variable
     tag and replace it with the appropriate variable data. More on this
     later.

     Placing the {1} variable tag on a line with the text (as shown above)
     will cause the BBS to clear the screen and place the text beside it on
     the first line. Placing the {1} variable tag on the a line by itself
     will cause the BBS to clear the screen and leave the first line blank.

     In the section that is displayed to the user, you can put any kind of
     character in the area. This would include something like the ESC
     character in order to use VT52, ANSI and other types of graphics.
     Anything that you want can be placed in this section. You can also do
     this with the Selection Prompt (line 2 of the Menu file). DO NOT use
     these ESC codes or whatever in the section used by the BBS except as
     noted above.

     It may be a good idea to name your Menu files with the extension of
     .MNU in order to easily pick out a Menu file from a plain .TXT (text)
     File. The extension of MNU is not required, just a suggestion.
























                                     - 66 -


     ONLINE GAMES

     Ok, using what you have learned above, I will try and show you the
     preferred method of setting up an Online Game. You may want to refer to
     the description of the ONLINExx.DAT file listed below in the DATA
     FILES section. here is an example.

     MENU
     Selection:
     5
     1 t J:\SEE\TODAY.TXT
     2 t J:\SEE\YDAY.TXT
     3 t J:\SEE\SCORES.TXT
     4 o 1
     5 Exit
     {1}Space Empire Elite
     ==================

     [1] Todays News
     [2] Yesterday's News
     [3] Player's Scores
     [4] Play Space Empire Elite
     [5] Exit

     In the above example, you will notice the '5 o 1' line. The '5' is
     what the user selects to cause the BBS to process this selection. The
     'o 1' tells the BBS to look for the ONLINE1.DAT file in the DATA
     folder. Again, refer to the description of the ONLINExx.DAT file in
     the DATA FILES section.

     I have a separate file that is seen first by the user that gives a
     list of the available games. When they choose an Online game from that
     selection, it will bring up another Menu like the one above. I have
     the above file named 'SEE.MNU' and when the user selects that games,
     the BBS will execute they SEE.MNU Menu which will in turn give the
     user the above options.

     That is all there is to setting up Menus and Online Games. I hope I
     have explained it clearly enough.





















                                     - 67 -


     DATA FILES

       The DATA files are files that are stored in the DATA folder. These
     can be files that you setup to make the BBS do certain things or files
     that the BBS itself uses. The ones that the BBS itself uses are not
     editable by the Sysop. A '(*)' beside the name of the file means that
     the file is a System file and is not editable by the Sysop.

     ALTDRV.DAT   (*)

     This is where the BBS stores the information for Alternate Drives for
     the File Areas. Alternate Drives can be defined in the File Area setup
     screen in the System Editor.

     ARCHIVE.DAT

     This is where you tell the BBS where to find the various archivers
     such as ARC.TTP, LHARC.TTP, etc. This is used for various functions
     that use these programs. Each line in this file must contain the
     drive, path and filename of the program. Each line must be kept in
     order. do not include the comments if you use this example to create
     the file. Nothing else can be on the line with the program name. if
     you do not have the file or do not plan on supporting this archive
     type, then leave the line blank. There must be the correct number of
     lines in this file which is 7.

     Example:
     H:\ARC\ARC.TTP              ; ARC program location and name.
     H:\ARC\LZH201L.TTP          ; LZH "                       "
     H:\ARC\ST_ZIP21\STZIP.PRG   ; ZIP "                       "
     H:\ARC\ZOO_201G\ZOO.TTP     ; ZOO "                       "
     H:\ARC\ARJ\UNARJ.TTP        ; ARJ "                       "
     H:\ARC\UNSIT\UNSIT.TTP      ; SIT "                       "
                                 ; BLANK LINE

     BACKUP.DAT

     This file is where you enter the filenames of the files you want
     backed up. This is done by the Cleanup program. This option is turned
     on in the Cleanup section of the System Editor. Each file must be on a
     separate line. The files are placed in the BACKUP folder.

     Example:


     BANNER.DAT   (*)

     This file is where the Banner program stores it's information. The
     Banner program allows you or users to enter in one liners that can be
     displayed wherever you place the variable tag for it in the
     PROMPT.DAT file or text files.

     Although this is is a file that a program stores it's information in,
     it is just a simple text file and you can add or remove items.






                                     - 68 -


     BBS_S.DAT    (*)

     This file is where the BBS stores the information for the Other BBSes.
     This is a System File. It goes along with the OTHERBBS command.

     BCPU.DAT

     This is where you enter the names of the computer types you want to
     Black List. When someone enters the Computer Type, the BBS will check
     this file and if it finds a match, it will not allow the person onto
     the system.

     Example:
     IBM
     AMIGA
     MAC

     BNAMES.DAT

     This is where you put the names of the people you want to Black List.
     When a person enters their name, the BBS will check this file and if
     it finds their name, it will not allow them onto the system.

     Example:
     John Doe
     Mary Jane

     BPHONE.DAT

     This is where you put the names of the phone numbers you want to Black
     List. When a person enters their phone number, the BBS will check this
     file and if it finds the number, it will not allow the person onto the
     system.

     Example:
     [phone]
     0292 34672

     CALLERS.INF  (*)

     This is where the BBS places the callers info for the Who's Called
     function. It will store the number of callers based on the 'Keep Last
     xx Callers' setting in the System Editor.

     COMMAND.DAT  (*)

     This is where the BBS stores the Command Tables that you set up in the
     System Editor.












                                     - 69 -


     COMPUTER.DAT

     This is where you place the name of the Computer choices a user has to
     choose from when the upload a file or the file is edited. If you have
     'Ask Computer Type' turned on for that File Area, then the BBS will
     look for this file and display it to the user when it wants to know
     what Computer Type the program is for. This is setup on the File Area
     setup screen in the System Editor. If the file does not exist, then
     the user will be able to enter in anything. If you have the option
     turned off, then the BBS will not ask for it and will just bypass the
     question.

     This is good if you have an Atari areas and want to be able to
     distinguish between Atari 8-Bit, Atari ST, etc. A maximum of 20
     Computer Types may be entered. Each type must be on a separate line
     and the file must have a blank line at the bottom. This is a global
     type file in that it will be for ALL File Areas if the COMP_xxx.DAT
     file is not found. This also helps keep the data that is entered
     consistent.

     Example:
     Atari ST
     Atari TT
     Atari 8-Bit

     COMP_xxx.DAT

     This works the same as the COMPUTER.DAT file above except, you can
     have a separate file for each File Area. xxx represents the File Area
     number.

     DEF_TAGS.DAT

     This file holds Sysop definable Variable Tags. This allows you to
     define your own variable tags to be used in text files, etc. You can
     have up to 100 tags defined. Each tag must be on it's own line. Please
     refer to the Variable Tags section for numbers to use for these tags.

     DOWNLOAD.LOG

     This file holds the information for downloads that have occurred. It
     will tell you the name of the user that downloaded a file, the file
     that was downloaded and the transfer protocol that was used. It will
     also show the CPS rating if the user did not use Zmodem. If they did,
     then the CPS rating will be 0. You can do whatever you want with this
     file. The program will create a new one if it isn't found.

     EDONE.DAT    (*)

     This is where the BBS stores the information for what Events have been
     executed.









                                     - 70 -


     EMULATE.DAT

     This is where you setup the types of Emulations you support. By
     Emulation, I refer to VT52, ANSI, etc. Each selection must match your
     TERMINAL.TXT file. If VT52 Color is on line 1, then choice #1 in
     TERMINAL.TXT must also indicate VT52 Color. Please refer to
     TERMINAL.TXT for information on that file.

     Example:

     ASCII
     VT52 Color
     VT52 Mono
     ANSI Color

     EVENTS.DAT   (*)

     This is where the BBS keeps the Event data. This is created by the
     System Editor when you setup your events.

     FTYPE.DAT

     This is where you place the information for File Type. File Type
     was designed to tell the user if the File is an LZH (LH5), LZH (LH1),
     GIF, ARC with folders, LZH with folders, etc. It can however be used
     for whatever you want to use it for. Each Type must be on a separate
     line and a blank line must be at the bottom of the file. You can enter
     up to 20 File Types.

     This is used when the user uploads a file and enters the description
     for that file. The BBS will ask the user to choose from one of the
     items in the list if you have this option turned on in the File Area
     setup in the System Editor.

     If this file does not exist, the BBS will allow the user to enter in
     any information they want. If the option is turned off, the BBS will
     not ask for this information.

     Example:
     ARC 5.xx
     ARC 6.xx
     ARC with Folders
     LZH (LH1)
     LZH (LH5)
     LZH with Folders
     Text
     Other

     FTYP_xxx.DAT

     This file works the same as the FTYPE.DAT file above except, it allows
     you to have a different file for each File Area. xxx represents the
     File Area number.







                                     - 71 -


     LOGOFF.BAT

     This is where you place the name of any program you want ran after a
     user logs off the system. The name of the file must include the drive,
     path and name of the file.

     If you want to pass a parameter to the program, just enter it after
     the name of the file, separated by a space.

     If you do not want this program to run after a local logon (you logon
     from the keyboard via the WaitCall screen), then you can place the
     word NOLOCAL after the filename or any parameter you may have.

     Each file you want executed must be placed on a separate line and a
     blank line at the end of the file.

     Example: J:\CALLTRAK\CALLINFO.PRG something NOLOCAL

     LOGON.BAT

     This is where you place the name of any program you want ran when
     someone logs onto the system. The name of the file must include the
     drive, path and name of the file. These file will be ran as soon as
     the BBS gets a CONNECT message from the modem.

     If you want to pass a parameter to the program, just enter it after
     the name of the file, separated by a space.

     If you do not want this program to run when you logon locally (from
     the keyboard via the WaitCall screen), then you can place the word
     NOLOCAL after the filename or any parameter you may have.

     Each file you want executed must be placed on a separate line and a
     blank line at the end of the file.

     Example: J:\CALLTRAK\CALLINFO.PRG something NOLOCAL

     LOGON1.BAT

     This works much the same way as the LOGON.BAT file except, it will
     only run AFTER the user has entered their name and password.

     MACROS.DAT   (*)

     This is where the BBS holds the Macro information for the user. It is
     created by the System Editor when you setup the Macro file.

     MASKS.DAT    (*)

     This is where the BBS holds the Mask information. The file is created
     by the System Editor when you setup the Mask file. It will store the
     information you setup in the Mask Editor portion of the User Editor.








                                     - 72 -


     MODEM.DAT

     This is where you put the information about what commands your modem
     uses for the various functions. In the example below is the commands
     the BBS will use if no MODEM.DAT file is found. The line numbers (1.,
     2., etc.) are only included as a reference and do not actually belong
     in the text file.

     Example:
     1. ATZ S0=1
     2. DTR
     3. ATH1 M0
     4. ATS0=0
     5. 5
     6. ATA
     7. RING
     8. 1
     9.

     Line 1: This is the RESET/ANSWER command that you want used. This is
     the command that the BBS will use to set the modem up to Auto-Answer.
     If you have S0=1 (turn Auto-Answer on) saved in the modem's memory,
     then you will not need the S0=1 after the ATZ command. Some modems
     will not recognize anything after the ATZ command. If your modem can
     store 2 or more setups, then you can use one for the BBS and one for
     your use. I have line 1 setup as ATZ1 since I have all the settings
     setup that are necessary for proper use for the BBS. I then use ATZ0
     on line 4.

     Line 2: This is the command you want used so that the BBS will tell
     the modem to HANGUP the phone. DTR just tells the BBS to toggle DTR
     off which if your modem is setup properly, will cause the modem to
     drop carrier (or hangup). Something like ATH0 can also be used.

     Line 3: This is the command you want used so that the BBS will tell
     the modem to take the phone OFFHOOK (answer the phone). This is used
     for when you logon locally, etc. where the BBS will have the modem to
     take the phone offhook so that nobody can call in and connect while
     you are doing something, etc. This line will also be used if you
     answer YES to the 'Take Phone Off the Hook' question when you go to
     eXit the BBS (item X on the WaitCall screen). If you answer Yes to
     this question, the BBS will not use Line 4.

     Line 4: This is the command you want used so that the BBS will tell
     the modem to take the phone OFFLINE. Normally this is S0=0 (turn
     Auto-Answer off). If your modem can store 2 or more setups, then you
     could setup one of those to do this and use a command like ATZ0. This
     is what I use since my modem can have 2 setups. This is used if you
     answer NO to the 'Take Phone Off the Hook' question when you go to
     eXit the BBS (item X on the WaitCall screen). It is also used when you
     use the DOS command from the Dos Shell (Sysop mode) which will Quit
     the BBS and take you back to the Desktop.








                                     - 73 -


     Line 5: This is where you tell the BBS how long to wait after a
     CONNECT message is received before it is to start sending out data.
     This was created due to high speed modems.

     When a high Speed modem calls a normal 1200, 2400, etc. baud modem
     that does not use MNP/Data Compression, the normal modem will start
     sending out data as soon as it receives the CONNECT message while the
     High Speed modem is still trying to negotiate other information. The
     result is that the user will not receive the first part of the
     information sent out by the BBS and the BBS will get garbage from the
     High Speed modem. This basically puts the BBS to sleep for this number
     of seconds.

       The Next 3 lines are only used if you have the BBS Answers Phone
     option turned ON on Settings Page 5 in the System Editor.

     Line 6: This is the command you want the BBS to send to the modem to
     answer the phone when it detects a RING or whatever is in line 7.

     Line 7: The is what the modem should look for when the phone rings.
     Normally it is set to RING.

     Line 8: This is the number of rings the BBS is to wait for before
     answering the phone.

     Line 9. This is a blank line.

     MONITOR.DAT

     This is where you place the information for the Monitor Type. This
     file was designed to tell the user what type of Monitor is required
     for this program to run on. It can however be used for whatever you
     want to use it for. Each entry must be on a separate line and a blank
     line must be at the bottom of the file. You can enter up to 20
     Monitors listed.

     This is used when the user uploads a file and enters the description
     for that file. The BBS will ask the user to choose from one of the
     items in the list if you have this option turned on in the File Area
     setup in the System Editor.

     If this file does not exist, the BBS will allow the user to enter in
     any information they want. If the option is turned off, the BBS will
     not ask for this information.

     Example:
     ST Color
     ST Monochrome
     ST Color/Mono
     ST/TT Color
     ST/TT Mono
     ST/TT Color/Mono








                                     - 74 -


     MONI_xxx.DAT

     This file works the same as the MONITOR.DAT file except, you can have
     one for each File Area. xxx represents the File Area number.

     NAMESxxx.DAT

     This is where you place the names that can be used with the 'Allow Any
     Name' option in the Message Base setup of the System Editor. If this
     option is ON, then the user has the choice of choosing a name they
     wish to save the message as. You provide the names in this list and
     the Level of the user that is required to use this name. There must be
     a blank line at the end of this file. You place the Name on one line
     and the level on the second line. You can have up to 10 names. xxx
     represents the Message Base number you want this list of names to be
     used in.

     Example:
     Joe Blow
     10
     Mary Jane
     10
     John Doe
     2

     NO_COM.INF

     This is where you tell the Cleanup what files with the listed
     extensions to not try and compress when it does the Auto-Compress
     function. This option is turned On or Off in the File Area setup
     screen in the System Editor. It is also turned On or Off with the
     Auto-Compress file Areas in the Cleanup section in the System Editor.
     The option in the File Area section only affects that File Area. The
     option in the Cleanup section affects ALL File Areas.

     Example:
     ARC
     LZH
     ZIP
     ARJ
     GIF



















                                     - 75 -


     ONLINExx.DAT

     This is where you enter in the information about an Online Game. It
     has a special layout that you must follow for it to operate properly.
     The example will be an extension of the example I used for online
     games in the Menu Processor section. All parameters must be separated
     by a space.

     You can have up to 99 ONLINExx.DAT files and up to 25 sets of
     information in each ONLINExx.DAT file. You must not leave any blank
     lines between the sets of information. You can of course only have 1
     set of information per ONLINExx.DAT file. This would allow you to
     group all the Space games together, all the Adventure games together,
     etc. The BBS will list each game out by it's name (Line 1).

     The ONLINExx.DAT files can also be used for other things besides games
     like the Fido network for example. Anything that uses the FOREM.DAT,
     TURBO.DAT, DORINFO1.DEF, etc.

     Example:

     Space Empire Elite        <--- Start of the first set of information
     2 NO


     J:\SEE_1021\SEE_1021.TTP LOCAL
     J:\SEE_1021\SEE_1021.TTP
     FOREM
     Overlord                   <--- Start of another set of information
     2


     J:\OVERLORD\OVERLORD.TTP LOCAL
     J:\OVERLORD\OVERLORD.TTP
     FOREM

     Line 1: This is the Name of the Online Game. It is not normally used
     unless you have more than 1 set of information in the ONLINExx.DAT
     file. This will also help you remember what this file goes with.

     Line 2: This is the level that is required by the user in order to
     play the game. This is based on the user's Online Game Level (OGL)
     that is defined in the User Editor under the Security Levels for that
     user.

     You can also place the word NO on this line as shown above. This will
     tell the BBS to not count this as an Online Game being played. It will
     not add the count to the user's information.












                                     - 76 -


     Line 3: This is the name of any file that you would want displayed
     BEFORE the game is executed. The name of the file would include all
     drive and path information also.

     Line 4: This is the name of any file you would want displayed AFTER
     the user exits the game and returns to the BBS. The name of the file
     would include all drive and path information also.

     Line 5: This is the name of the file to execute if the user is on
     Locally. This is normally the Sysop at the keyboard. Some programs
     require the LOCAL parameter (as seen above) to let it know that the
     user is on locally. Some (I have seen one) use a separate program for
     local playing. The name of the program would include the drive and
     path information also.

     Line 6: This is the name of the file to execute if the user is calling
     in (remote user).

     Line 7: This is the type of DAT file you want written to the Online
     games directory before the BBS executes the program. The following
     is a list of the available options.

     FOREM - Write a FOREM.DAT and a DORINFO1.DEF file to the program's
     directory.

     TURBO - Write a TURBO.DAT and a DORINFO1.DEF file to the program's
     directory.

     TRANS - Writes a TRANUSER.INF file to the program's directory. This is
     our own data file. The layout of this file is located in the
     Appendices.

     DOORINFO - Writes a DORINFO1.DEF file to the program's directory.

     STAR - Writes a USER.TMP file to the program's directory. This is a
     STARNET BBS compatible USER.TMP file for games written for that BBS
     program.

     OTHER - Writes the user's Handle to a file called USER.INF to the
     program's directory.

     If none of the above choices are given, then the BBS will default to
     writing a TRANUSER.INF file to the program's directory.

     PROTOCOL.DAT (*)

     This is where the BBS gets it's information on the different
     Protocols, their key required to select it and the filename to execute
     for this Protocol. This file is created by the System Editor when you
     setup the Protocols.










                                     - 77 -


     QUESTION.DAT

     This is where you tell the BBS what user questions to ask the user
     when they apply for an account. Each line represents a question that
     the BBS normally would ask a new user or will ask the user if this
     file is not found. The text beside each YES is just for reference. If
     you do not want this question asked, then replace YES with NO. do NOT
     alter the size of this file. There must be the correct number of
     entries in this file.

     Example:
     YES     Ask if they want an permanent account at logon?
     YES     Ask Video Height?
     YES     Ask Video Width?
     YES     Ask Users Name (You can't turn this off)
     YES     Ask Users Handle?
     YES     Address?
     YES     City?
     YES     Zip Code?
     YES     Phone Number?
     YES     Computer type?
     YES     State?
     YES     Country?
     YES     Password (You can't turn this off)
     YES     Users Age
     YES     Users Sex
     YES     Ask Second (Data) Phone Number?

     SYSOP.LOG

     This is where the BBS stores the information you tell it to. You can
     save a message, etc. to this file for future reference. Anytime you
     see an option of [L]og (in Email, etc.), then when you choose this
     option, the BBS will ask you where to save it to. The Sysop's log is
     one of those choice. You can do whatever you want with this file. If
     it is not found, the BBS will create it.

     TRANS.DAT    (*)

     This is where the BBS gets 90% of it's setup information. This file is
     created by the System Editor when you do a Save TRANS.DAT. It must
     reside in the same directory as TRANSBBS.PRG.


















                                     - 78 -


     TYPE.DAT

     This is where you place the information for Program Type. Program Type
     was designed to tell the user what type of program the file was such
     as a Game, Application, BBS, Telecom, etc. You can however use it for
     whatever you want to use it for. Each entry must be on a separate
     line and a blank line must be at the bottom of the file. You can enter
     up to 20 Program Types.

     This is used when the user uploads a file and enters the description
     for that file. The BBS will ask the user to choose from one of the
     items in the list if you have this option turned on in the File Area
     setup in the System Editor.

     If this file does not exist, the BBS will allow the user to enter in
     any information they want. If the option is turned off, the BBS will
     not ask for this information.

     TYPE_xxx.DAT

     This file is like the TYPE.DAT file above except, you can have a
     different one for each File Area. xxx represents the File Area number.

     UPLOAD.LOG

     This is where the BBS places information about uploads. It will tell
     you who the uploader was, what file was uploaded, what File Area it
     was uploaded to and the protocol used. You can do whatever you want
     with this file. If the file is not found, the BBS will create it.

     USERS.DAT    (*)

     This is where all the user's information is stored. It is initially
     created by the System Editor but is updated by the BBS.

     USERS.IDX

     This is an Index file that goes along with the USERS.DAT file.

     USERS.TXT

     This is where you enter in information for the Print User program.
     Please refer to that section for instructions on setting up this file.

















                                     - 79 -


     WAITCALL.DAT

     This is where you can place program names that you want to be able to
     be ran from the WaitCall screen. The BBS will fill the empty slots
     (letters not used) with this programs name. You can then execute the
     program by simply pressing the corresponding letter. There must be a
     blank line between each entry. If you wish to have any parameters
     passed onto the program, then you must place them beside the filename
     with a space between the filename and the parameter.

     Example:
     Flash
     C:\FLASH\FLASH.PRG

     Gem System Editor
     J:\SYSEDITG.PRG

     Arc Shell
     H:\ARC\ARCSHL31.PRG

     Isis Mail
     J:\INTERBBS\ISISMAIL.PRG something

     WELCOME.BAT

     This is where you place the name of any program you want ran when
     someone logs onto the system. The name of the file must include the
     drive, path and name of the file. These file will be ran as just
     before the WELCOME.TXT file is displayed.

     If you want to pass a parameter to the program, just enter it after
     the name of the file, separated by a space.

     If you do not want this program to run when you logon locally (from
     the keyboard via the WaitCall screen), then you can place the word
     NOLOCAL after the filename or any parameter you may have.

     Each file you want executed must be placed on a separate line and a
     blank line at the end of the file.

     Example: J:\CALLTRAK\CALLINFO.PRG something NOLOCAL



















                                     - 80 -


     TEXT FILES

       Text Files are files which the BBS uses to display information to
     the user. These are plain ASCII files that can be edited by the Sysop.
     These files allow you to customize your BBS so that the BBS can take
     on the look that YOU want. These files are located in your TEXT folder
     and in one of the MENUSx folders.

     The MENUSx folders represent the different types of emulations you
     have. 'x' represents the number that the user chooses for the type of
     emulation he wants. For instance, you want all ASCII text files in
     MENUS0, VT52 files in MENUS1, ANSI files in MENUS2, etc. When the user
     chooses what type of emulation he wants from the TERMINAL text file,
     the BBS will switch to that MENUSx folder to locate and read in the
     appropriate text file. If the file is not found, the BBS in most cases
     will switch to MENUS0 (default) to try and find that file. If found,
     it will display it.

     This allows you to only change the files you want to display in the
     emulation and the rest will be taken from the MENUS0 folder. In order
     to make these files display in different emulation styles, you will
     have to edit them and place the proper codes into the file. With this
     method, you can have just about any type of output you want. All Text
     Files are editable by the Sysop. Special formatting may be required
     and will be noted in the description of that file.

     Although these text files were designed to be used for specific
     purposes, you can use them for anything you desire. You can change
     them to look the way you want, make MENUS out of them, or whatever you
     want.

     Some of these text files are tied to the Built in Procedure Commands.
     This means that when a user chooses the command from one of the menus
     using the key you defined, then this text file will be displayed. The
     Built in Procedures that these files are tied to will be given in the
     description such as 'COMMAND: PARMEDIT'. This would mean that that
     text file was tied to the Built in Procedure PARMEDIT which is used
     int he Command Tables in the System Editor.

     Some of the text files will have one or more x's in it's name. This
     usually deals with a File Area number, Message Base number or a
     sequence of text files that will be displayed one after the other
     going from FILE.TXT to FILE1.TXT to FILE2.TXT, etc. until it runs out
     of those files.

     ALRDCHAT.TXT

     This file is displayed when the user has reached their Max. Pages per
     Call Limit.

     Example:

     {1}
     Enough already! I am either not here, in bed or I do not want to chat.
     Leave Feedback if it that important.





                                     - 81 -


     BASExxx.TXT

     This file is displayed anytime a user enters a Message Base. This is
     different from MTOPxxx.TXT in that it is displayed everytime a user
     enters the Message bases versus only when the user first enters the
     Message Base. Use it to tell the user what the topic of the Message
     Base is or whatever.

     Example: BASE1.TXT

     This Message Base is for General Chit Chat. If there is a specific
     Message Base for a topic, then please use that Message base.

     BBSADD.TXT

     This file is displayed when a user goes to add a BBS to the Other BBS
     Listing. Use it to place instructions to the user or whatever.

     BBSLIST.TXT

     This file is displayed when a user does a listing of the available BBS
     in the Other BBS listing. It is used to display the available options
     to the user.

     Example:

     BBS List
     ========

     [A]dd to the List
     [V]iew the List
     [E]dit BBS List
     [Q]uit to main menu

     If this file is not found, the BBS will display a built in menu. The
     big difference is that the BBS will check to see if the user has the
     appropriate access level (255) and if not, it will not display the
     '[E]dit BBS List' menu option.

     BBSVIEW.TXT

     This file is displayed when the user chooses to get a Listing of the
     BBS's in the Other BBS section. It is used to display a list of the
     available options that the user can choose from. If this file is not
     found, the BBS will use a built in Menu of the options available.

     Example:

     Search Methods:

     [1] - Name
     [2] - Phone Number
     [3] - Comments
     [4] - Software
     [5] - All

     Select:



                                     - 82 -


     BDAY.TXT

     This file will be displayed when the BBS detects that it is the
     user's birthday.

     Example:

     Happy Birthday to you.
     Happy Birthday to you.
     Happy Birthday Dear {3}.
     Happy Birthday to you.

     CALLSYS.TXT

     COMMAND: CALLSYS

     This file is displayed when a user Pages the Sysop.

     Example:

     O Sysop, impart on me some of your wisdom. Let's chat sucker...

     CALLS.TXT

     COMMAND: VIEWCALL

     This file is used to define the way the output for the Who's Called
     Listing is displayed to the user. This file uses variable tags 137 -
     142. It is used in conjunction with Prompt number 223 in the
     PROMPT.DAT file. The prompt is shown first and then the BBS will step
     through the list of the Last x number of Callers using this layout.
     'x' represents the number of callers you tell the BBS to keep track
     of. This is set in the System Editor in the Settings section. If this
     file is not found, the BBS will default to a built in output. The
     actual information is stored in the CALLERS.INF file located in the
     DATA folder.

     Example:

     {137p8} {138p30} {139p8} {140p5} {141p8} {142p8}
     blank line goes here

     The output would look something like...

     Caller# Handle                          Date   Baud  On Time  Off Time
     ------- ----------------------------- -------- ----- -------- --------
     189     Wayne Watson                  01/14/93 14400 04:30 pm 04:50 pm
     188     John Johnson                  01/14/93 2400  02:30 pm 03:30 pm
     etc.

     The header at the top of this listing is prompt # 223 in the
     PROMPT.DAT file located in the TEXT\MENUSx folder(s).








                                     - 83 -


     CARRIER.TXT

     This file is one of the very first files to be displayed when a user
     logs on. It is displayed as soon as the BBS gets the CONNECT message.
     It can be used for anything you wish. It is also displayed during a
     local logon.

     CAT.TXT

     This file is used to control how the output for a Catalog Listing is
     displayed to a user. If this file is not found, the BBS default to a
     built in output format. It is used in conjunction with Prompt number 36
     and 53 in the PROMPT.DAT file. There are two lines you must define in
     this file. Line one is used for the normal Catalog Listing and Line
     two is used for the Continuous Catalog Listing. This line will be
     shown when the user has Continuous Scroll turned on in the File Areas.
     This file uses tag numbers 303, 304, 308, 322, 334 and 335. You can
     add VT52, ANSI, etc. control codes to make the output look
     differently.

     Example:

     [{335}] {322p5} {303p12} {304p7} {308} {334}
     {322p5} {303p12} {304p7} {308} {334}

     The output for a regular Catalog Listing would look something like...

      Key File# Filename     Bytes     Date   Brief Description
      --- ----- ------------ ------- -------- -----------------------------
      [A] 12345 ARC.TTP      134980  01/14/93 Latest version of ARC.
      [B] 12346 LHARC.TTP    12390   01/14/93 Latest version of LHARC.
      etc.

     The output for a Catalog Listing with Continuous Scroll on would look
     something like...

      File# Filename     Bytes     Date   Brief Description
      ----- ------------ ------- -------- ---------------------------------
      12345 ARC.TTP      134980  01/14/93 Latest version of ARC.
      12346 LHARC.TTP    12390   01/14/93 Latest version of LHARC.
      etc.

     The header for the first listing is prompt # 53. The header for the
     second listing is prompt # 36 in the PROMPT.DAT file in the
     TEXT\MENUSx folder(s).

     CAT_xxx.TXT

     This file is basically the same as CAT.TXT. The only difference is
     that by using the File Area number (xxx), you can have a different
     CAT.TXT file for each area. The BBS will search for this file first,
     if it is not found, it will then search for CAT.TXT and if it is not
     found, it will use the built in displaying of the files. Number range
     from 1 to 256.






                                     - 84 -


     CLEARSCR.DAT

     This file allows you to define what keycode sequence that will clear
     the screen for that emulation. If you had VT52 in MENUS1, then you
     would have something like 'ESC E' for VT52 screen clearing. You could
     also have this file in other MENUSx folders for different emulations
     that use a different clear screen code.

     Example: TEXT\MENUS1\CLEARSCR.DAT

     {ESC}E

     The above example assumes you have VT52 text files in MENUS1. The
     {ESC} is the escape character. This would clear the screen for most ST
     systems calling in since the ST has VT52 built in. You can have a
     CLEARSCR.DAT file for each type of emulation and place it in the
     appropriate MENUSx folders.

     CONNECT.TXT

     This file is displayed upon connection.

     Example:

     NOABORT
     {1}
                                   Welcome to {41}

                                  300/1200/2400 Baud

                                  Sysop: {39}

                               You are caller number: {30}

     CONNECTxx.TXT

     This file is basically the same as the CONNECT.TXT file except it is
     the next file to be displayed in sequence after the CONNECT.TXT file.
     You can have up to 99 CONNECTxx.TXT files.





















                                     - 85 -


     DOSMENU.TXT

     This file is displayed when you enter a '?' at the Sysop Dos Shell. It
     will give you a detailed description of the available commands.

     Example:

     Syntax                                       Description
     ====================================================================
     ?, HELP                                      This Menu
     UEDITOR                                      User Editor
     RESERVE user                                 Reserve BBS
     CHAT, C                                      Chat Mode
     CHAT on/off/normal                           Set Chat Status
     CHAT STATUS                                  View Chat Status
     EXEC [EX] filename                           Execute File
     BATCH filename                               Execute Batch File(s)
     GEM ON                                       Gem Mode
     TIME current time                            View/Change Time
     DATE current date                            View/Change Date
     TERM                                         Terminal Mode
     SEND filename                                Send File
     RECEIVE filename                             Receive File(s)
     BSEND, SENDB                                 Send Batch Marked Files
     MARK filename/filelist                       Batch Mark File(s)
     VIEWMARK                                     View Marked Files
     UNMARK                                       Unmark File
     CLEARMARK                                    Clear Batch List
     TYPE filename                                Display Text File
     TEST filename                                Display Text/Menu_File
     CHKDSK drive                                 Disk information
     MKDIR [MD] foldername                        Make Folder
     RMDIR [RD] foldername                        Delete Folder
     RENAME [RN] filename1 filename2              Rename File
     EDIT [ED] filename                           Text Editor
     DELETE [DE], KILL, ERASE filename/list       Delete File(s)
     COPY [CO] filename1/list1 filename2/list2    Copy File(s)
     MOVE [MO] filename1/list1 filename2/list2    Move File(s)
     VERBOSE filename                             View Archive
     TOUCH filename                               Update File Date & Time
     DIR path                                     Directory
     CD, CHDIR, CWD                               Change Drive/Path
     HANG UP                                      Hang Up User
     STATUS                                       BBS Status
     RERUN                                        Re-Load Transcendence
     Q, EXIT                                      Exit DOS mode
     DOS                                          Exit To GEM













                                     - 86 -


     DOWNLOAD.TXT

     COMMAND: DOWNLOAD

     This file is displayed when a user chooses the Download or Mark File
     option from the main File Menu. It just briefly tells the user how to
     use the Download/Mark File feature.

     Example:

     To download a file, just type in the name or number at the '>' prompt.
     Separate the name/number by a ',' to download more than one file.
     Press <RETURN> to obtain another line to enter more names/numbers or,
     to end entry, press <RETURN> at the '>' prompt.

     EDITUSET.TXT

     COMMAND: SETTINGS

     This file is displayed when a user uses the SETTINGS command. It
     displays the user's current settings.

     Example:

     {1}User Settings:
     []==========[]

     [0] Default terminal type: {101p12}  [1] Default window size: {102}
     [A] Auto read email      : {103p12}  [B] End of page pause  : {104}
     [C] Hotkey commands      : {105p12}  [D] Command stack prnt : {106}
     [E] Clear screen         : {107p12}  [F] Default compression: {108}
     [G] Continuous scroll msg: {109p12}  [H] Pause between msgs : {110}
     [I] File area prompts    : {111p12}  [J] Msg base prompts   : {112}
     [K] Word wrap in editor  : {113p12}  [L] Line numbers in edt: {114}
     [M] Scan/mark messages   : {115p12}  [N] Editor summary     : {116}
     [O] Auto scan messages   : {117p12}  [P] Auto scan new files: {118}
     [Q] Emacs text editing   : {119p12}  [R] New files scan list: {120}
     [S] Default protocol     : {318p12}  [T] Key aborts text    : {121}
                          [U] Terminal width/height: {14}x{15}
     [Return] Finished                        [?] Show Again

     EMAIL.TXT

     COMMAND: EMAIL

     This file is displayed when a user uses the EMAIL command. It is used
     to display the commands available to the user.

     Example:

     {1}
                            Southern Software BBS E-mail System
                            -----------------------------------

                                 [F] F-Mail Send
                                 [R] Read E-Mail/F-Mail
                                 [S] Send E-Mail/F-Mail

                                 [Q] Exit E-/F-Mail System

                                     - 87 -


     EMAILFUL.TXT

     This file is displayed when there are no more Email slots available
     and a user tries to leave Email or Feedback to someone.

     Example:

     Sorry, the Email system is full right now.
     The Sysop has been informed, and will correct this problem ASAP.
     Please try again later.

     EMAILHLP.TXT

     This file is displayed when a user enters a '?' at the 'Send Mail To:'
     prompt.

     Example:

     Enter the users handle to send mail to.  If you are not sure of the
     spelling, enter part of it.  The BBS will then search for any user who has
     what you type, in their handle.  For Example:

     To Who (?=Help): David Br

     The BBS will return:

     Partial match found "David Brown" is this correct?

     Press [Return] to abort Email send

     EMAILSND.TXT

     This file is displayed when the user chooses the Send Email option in
     the Email section. It can be used to give instructions on using Email,
     etc.

     Example:

     Enter the users handle to send mail to.  If you are not sure of the
     spelling, enter part of it.  The BBS will then search for any user who has
     what you type, in their handle.  For Example:

     To Who (?=Help): David Br

     The BBS will return:

     Partial match found "David Brown" is this correct?

     Press [Return] to abort Email send or ? for Help.

     ENTSYSOP.TXT

     This file is displayed when the Sysop goes into the Sysop Mode (Dos
     Shell) and chooses not to allow the user to see what is happening.

     Example:

     Please Standby. Sysop using System.


                                     - 88 -


     EXITCHAT.TXT

     This file is displayed when the Sysop quits out of Chat with a user.
     This is only used when the Built in Chat mode is used (CALLSYS).

     Example:

     Now leaving, The Sysop Zone...

     FAREAS.TXT

     This file is displayed when a user uses a command that causes the BBS
     to display a list of the available File Areas. If this file is not
     found, the BBS will generate a list of available File Areas. This
     built in list will only display the File Areas available to the user.
     If they do not have access to a File Area, the BBS will not show it to
     the user and the File Area numbers will be in numerical order. They
     will not even realize they are missing anything. The FAREAS.TXT file
     does not have this ability but, it allows you to set up the display of
     the available File Areas the way you want.

     Example:

     {1}
                         Southern Software Files Areas
                         -----------------------------

             [1] General Files           [4] ST Telecommunications
             [2] ST Utilities            [5] Spectre/Mac
             [3] ST Applications
                                  [N]ew Files


     FHDRxxx.DAT

     This file allows the Sysop to define the way the header, for the Long
     description of a file, is displayed. The header provides all the
     information about the file being displayed such as, Filename,
     Filesize, Uploader, Upload Date, Type of File, number of downloads,
     etc. This allows the Sysop to define what information is to be
     provided and how it is to be presented. Numbers range from 0 to 256.
     If a FHDR0.DAT file is present, it will be used as a header for ALL
     File Areas unless a FHDRxxx.DAT file is found. For instance, if you
     created a FHDR1.DAT file to be used for File Area 1, then this file
     header will override the FHDR0.DAT file.

     Example:

     Filename       : {303p12} (#{322p5}) {317p4}Status    : {312}
     Uploaded       : {308p8} at {307p8} {317p5}Uploader  : {306}
     File Type      : {305p25} Level     : {311}
     File Size      : {304p7} {317p18}Downloads : {310} time(s)
     Last Downloaded: {309p8} {317p17}Xfer Time : {316} at {33} Baud
     Computer Type  : {313p25} Monitor   : {314}
     Blocks         : {324} Xmodem, {325} Y/Zmodem, {326} Fmodem

     {315}



                                     - 89 -


     FILEMENU.TXT

     This file is displayed when a user chooses the Sysop defined key for
     Help in the File Area Command Table. This provides the user with a
     list of Commands that are available for the File Areas.

     You will need to enter the name of this text file in the FILENAME
     field in the File Area Command Tables with the key of your choice.

     Example:

     {1}                    {41} BBS File Menu

       [A] ARC D/L Utilities                   [R] Read a Text File
       [B] Batch Download Marked Files         [S] Search for File Since Date
       [C] Catalog Files (No Description)      [T] Toggle Continuous Scroll On/Off
       [D] Download A File                     [U] Upload A File
       [E] Edit File Scanning List             [V] View Marked Files
       [F] Find A File                         [W] Search Contents of Files
       [G] Goodbye (Log Off)                   [X] Exit File Area
       [K] File Maintenance                    [Y] Wide Listing
       [L] List Files (With Description)       [+] Next File SIG
       [M] Mark File for Batch D/L             [-] Previous File Sig
       [N] List ALL New Files                  [=] Goto Another File Area
       [Q] Exit File Area                      [?] This Menu (Help!)

     FMAIL.TXT

     This file is displayed when the user chooses the Send Fmail option in
     the Email section. It can be used to give instructions on using Fmail,
     etc.

     Example:

     At the Fmail Filename prompt, enter in the name of the file as you
     want it called.

     You can enter part of the name at the To: prompt and the BBS will try
     and find a match for you. It will present you with a list of names
     that it found and you can choose if this is the user you are looking
     for.

     FTOPxxx.TXT

     This file is displayed anytime the user enters a File Area. xxx
     represents the File Area number. If for instance, a user enters File
     Area number 1, then the BBS will look for FTOP1.TXT and display it if
     found. This was designed to let the user know what files are to be
     uploaded in this File Area, etc. Numbers range from 1 to 256.

     Example: FTOP1.TXT

     This File Area is for General files that normally are not computer
     specific such as text files, etc.






                                     - 90 -


     GOCHAT.TXT

     This file is displayed when the Sysop enters the Chat Mode with a
     user.

     Example:

     Now Entering The Sysop Zone...

     GR_RESET.TXT

     This file is used to reset the users colors, etc. so that when a user
     aborts output of information using Control-C, it will not leave the
     BBS or the users screen in a mess. When Control-C is used, the BBS
     will then look for this file and send out the information contained in
     it. Place one of these files in each of the MENUSx folders so that the
     user's screen can be reset based on the emulation type they have
     chosen.

     HANGUP.TXT

     This file is displayed when the Sysop kicks a user off the system
     using the F10 function key.

     Example:

     {1}

     System Coming Down For Sysop Maintenance.
     Please Call Back Later!

     HELP.TXT

     This file is displayed when the HELP key is pressed on the keyboard.
     It was designed to display the available functions keys and what they
     do.

     Example:

                                Function Keys

      Normal                              Alternate

      [F1]  Sysop Mode/Dos Mode           [F1]  Restricted Access Toggle
      [F2]  Chat Mode                     [F2]  Chat with Capture
      [F3]  User Editor                   [F3]  Add 10 Min.
      [F4]  File Maintenance               [F4]  Add 1 Min.
      [F5]  Change Window Size            [F5]  Sub. 10 Min.
      [F6]  Local Reserve                 [F6]  Sub. 1 Min.
      [F7]  Reset Vt52                    [F7]  Disk Capture Toggle
      [F8]  Printer Toggle                [F8]  Window Hide/Show
      [F9]  Snoop Toggle                  [F9]  Alert Mode OFF
      [F10] Hangup & display HANGUP.TXT  [F10]  Hangup & display Garbage

           Shift
           [F1]  Toggle Screen Saver On/Off
           [F2]  Select Chat Mode Status

                               Press Any Key To Continue...

                                     - 91 -


     LOCK_xxx.TXT

     This file will be displayed when a user logs on and they have been
     locked out. By using the [L]ock/Unlock command in the User Editor, you
     can lockout a user and assign them a number. This number will
     correspond to the xxx part of the filename. For instance, if you did
     not want people with Blonde hair to log on, you could lockout a user
     in the User Editor and assign that user the number 1. In LOCK_1.TXT,
     you could put something like, "You are not allowed on this BBS because
     you have Blonde Hair" or something like, "The BBS is currently down
     for Maintenance". Everytime they call, the BBS will down to them.

     You can have a number from 1 - 255. If you did not want to permanently
     BlackList a user and just wanted to antagonize the user, then this
     is the way to do it.

     LOGOFF.TXT

     This file will be displayed when a user logs off the BBS. This will be
     either using the GOODBYE option you defined or by typing the word OFF
     at any prompt.

     Example:

     Have a good day {2}!

     Thanks for calling
     Southern Software BBS

     Ya'll come back now, hear...

     C L I C K ! ! !
     {98-3}

     LOGOFFxx.TXT

     This file is the same as the LOGOFF.TXT file but, it is just another
     file in the sequence. You can have up to 99 LOGOFF text files.

     LOGSTAT.TXT

     This file is part of the LOGON sequence and was designed to show the
     user the STATS at logon.

     Example:

     {1}
                               Name     : {3}
                               User No. : {17}
                  -----------------------------------------
                            Todays Date : {28}
                            Current Time: {34}
                  -----------------------------------------
                  Your Minutes On Today:........ {23}
                  -----------------------------------------
                  Your Time Limit Per Day:...... {21} Min
                  Your Time Limit Per Call:..... {22} Min

                         Last Caller was {31}

                                     - 92 -


     LOGSTATxx.TXT

     This file is basically the same as the LOGSTAT.TXT file except it is
     the next in sequence after the LOGSTAT.TXT file. You can have up to 99
     LOGSTATxx.TXT files.

     MAC_HELP.TXT

     This file is displayed when the user request help in the Macros
     Editor. It just gives some information on using the macros.

     Example:

     {1}
     Macro Keys
     ----------

       With Transcendence you may define macro keys.  The number of keys
     you may define, and their length is decided by your Sysop. A macro
     key simply replaces a long string of text with a couple keystrokes.
     A good example of using this is for users who like to put their
     name/handle at the end of each message, instead of typing it each time
     you can define a macro as your name, and call that macro each time.

       To define a macro, go into the macro editor from the main menu. Type
     the number of the macro you want to change. Simply type in whatever
     you want. To put a "Return" character in your macro, place "@C" in it.
     To put an "@" symbol, put two @'s in a row (ie. "@@").

       You may use Escape codes in your macros also.

       To call up the macros, hit ^A (Control-A).  Then press a number 1
     to 0. 0 would be macro key #10. If you have more than 10 macro's to
     use, call number 11-20 by pressing A-P on your keyboard, 'A' would be
     macro #11, and 'P' would be macro #20.

       It takes a little getting used to, but it is a big time saver after
     you get used to it.
     {47}





















                                     - 93 -


     MAINMENU.TXT

     This file is displayed when the user chooses the Help key (normally
     defined as a '?') from the Main Menu. It shows the user the available
     commands and the keypress required to activate that command. The
     actual key for the Help command is defined by the Sysop in the Command
     Tables in the System Editor. You can however, name this file anything
     you want. Just make sure you have the same name defined in the
     System Editor. If no path is given, then the BBS will look for the
     file in the TEXT\MENUSx folder. You must have this file defined as a
     Text/Menus/Script file.

     Example:

     {1}
                               Southern Software's Main Menu
                               -----------------------------

            [A] Set Terminal Type                   [O] Other BBS's
            [B] New Files Scan                      [P] Edit Your Parameters
            [C] Call for Sysop                      [Q] QuickScan Messages
            [D] Library (Help Files)                [R] Recreation Room
            [E] Email/Fmail System                  [S] Edit User Settings
            [F] File Areas                          [T] Send New Messages
            [G] Goodbye (Log Off)                   [U] User Listing
            [H] Handles of Users                    [W] Who's Called
            [J] Jump to a Message Base              [Y] Your Statistics
            [L] Leave Feedback                      [Z] Macro Editor
            [M] Message Bases                       [=] Go to a Message Base
            [N] System News                         [?] This Menu (Help!)

     MAREAS.TXT

     This file is used to display the available Message Bases that the user
     can choose from. If this file is not found, the BBS will use a built
     in display that will display the available Message Bases. The
     difference between MAREAS.TXT and the built in display is that the
     built in display will not show a user a Message Base if the user does
     not have access to it. Also, with the MAREAS.TXT file, you can make
     the display look like you want. There is a trade off here.

     MARKBASE.TXT

     COMMAND: MARKBASE

     This file will be displayed when the MARKBASE option is used. It was
     designed as a header to be displayed before the BBS shows the user
     what Message Bases they can choose from to turn On or Off for their
     QuickScans, etc.

     Example:

     {1}
                              Select Bases For Your QuickScan
                              * * * * * * * * * * * * * * * *





                                     - 94 -


     MARKFILE.TXT

     COMMAND: MARKFILE

     This file will be displayed when the MARKFILE option is used. It was
     designed as a header to be displayed before the BBS shows the user
     what File Areas they can choose from to turn On or Off for their
     QuickScans, etc.

     Example:

     {1}
                           Select File SIGs For Your QuickScan
                           * * * * * * * * * * * * * * * * * *

     MEDITOR.TXT

     This file is displayed before a user starts editing a message. It was
     designed to give the user a list of the available options for the
     Message Editor. The user can turn off this help file in their
     Settings which uses the SETTINGS command. If they have Message Editor
     Summary turned OFF, the file will not be displayed.

     Example:

     {1}
                           {41} Message Editor Commands

                          Precede ALL commands with a '/'

       [A] Abort Message       [Ixx] Insert xx Blank Lines   [T] Goto Top
       [B] Goto Bottom         [Lxx] List Next xx Lines      [W] Word Wrap On/Off
       [C] Center Text           [L] List Without Line #'s   [Y] Change FROM
       [D] Delete ALL Lines      [N] List With Line #'s      [#] Line #'s On/Off
     [Dxx] Delete Next xx Lines  [P] Preview Message       [Gxx] Goto Line xx
       [S] Save Message         [SP] Save Private           [SF] Save with File
       [?] Help                 [Exx] Edit Line xx
       [R/xxx/yyy] Replace xxx with yyy - Must be in Edit Mode






















                                     - 95 -


     MEDITOR2.TXT

     This file is displayed if the user request Help in the Message Editor.
     This file was designed to give more information on the available
     commands in the Message Editor. It is more of a Extended Help type of
     file. The user can request help by entering /?<Return> or
     /HELP<Return>. The /HELP is not case sensitive.

     Example:

     {1}
     Message Editor Commands
     xx = Line number you want.

     /A     -  Used to abort the message
     /B     -  Used to take you to the bottom of the message
     /C     -  Used to center the text on the current line number
     /D     -  Used to delete ALL lines in the message. Will ask if you are sure.
     /Dxx   -  Used to delete the next xx number of lines.
     /Exx   -  Used to edit xx line number. Puts you in Edit Mode.
     /Gxx   -  Used to go to line number xx.
     /Ixx   -  Used to Insert xx number of lines before the current line number.
     /L     -  Used to List the message.
     /Lxx   -  Used to List the next xx number of lines.
     /N     -  Used to list the lines in the message with line numbers.
     /P     -  Used to preview the message. Will show what it will look like.
     /R/xxx/yyy - Used to replace the word xxx with the word yyy. Must be in Edit
                  mode. Use /Exx to put you in Edit Mode.
     /S     -  Used to save the message.
     /SF    -  Used to save the message with a file attached.
     /SP    -  Used to save the message as a private message.
     /T     -  Used to go to the Top of the message.
     /W     -  Used to toggle Word Wrap On/Off.
     /Y     -  Used to change the From field. Only if you are allowed to do so.
     /?, /H -  This help file.
     /#     -  Used to turn line numbers On/Off.

     {47}

     MHDRxxx.DAT

     This file allows you to design your own Message Header. If this file
     is found, then the BBS will display it instead of the built in Message
     Header. The Message Header is the part that gives all the information
     about the message such as From, To, Status, etc. xxx represents the
     Message Base number. If a MHDR0.DAT file exist, then the BBS will use
     this file header for ALL Message Bases unless a FHDRxxx.DAT file
     exist. For instance, if a MHDR1.DAT file to be used for Message Base 1
     exist, then it will be used instead of MHDR0.DAT.











                                     - 96 -


     MSGMENU.TXT

     This file is displayed when the user chooses the Help key (normally
     defined as a '?') from the Message Menu. It shows the user the
     available commands and the keypress required to activate that command.
     The actual key for the Help command is defined by the Sysop in the
     Command Tables in the System Editor. You can however name this file
     anything you want. Just make sure you have the same name in the
     Command Tables. If no path is defined and only the Filename is given,
     then the BBS will look in the TEXT\MENUSx folder for the file. You
     must have this file defined as a Text/Menus/Script file.

     Example:

     {1}                 {41} BBS Message Menu

       [B] Backward Read Messages              [R] Read an Individual Message
       [C] Check Messages To/From You          [S] Search Message for Keywords
       [E] Enter a Message                     [T] View Topic of Message Base
       [F] Forward Read Messages               [U] User List
       [G] Goodbye (Log-off)                   [V] View Marked Messages
       [H] Set High Message Counter            [X] Exit Message Area
       [I] Information on Message Base         [+] Next Message Base
       [M] Mark Message Base for QuickScan     [-] Previous Message Base
       [N] Read All New Messages               [=] Goto A Message Base
       [P] Post A Message                      [?] This Menu (Help!)
       [Q] Exit Message Bases

     MTOPxxx.TXT

     This file is displayed when a user enters a Message Base for the first
     time or, anytime their High Msg Counter is at 0. It was designed to
     tell the user what the topic of the Message Base is. xxx represents
     the Message Base number.

     Example:

     {1}This is the General Message Base. It is the place to post
     messages not directly covered in the other bases. Also you will find
     information about the BBS in this base.

     NEWEMAIL.TXT

     This file is displayed when a new user logs on the the New User Email
     setting in the System Editor is ON. It just tells the user that they
     will now be asked to enter Email to the Sysop.

     Example:

     {1}
     At this point you need to leave a message to the Sysop.  Please tell
     the Sysop a little about yourself, and why you would like access.
     {47}







                                     - 97 -


     NEWUSER.TXT

     This file is displayed when a user logs on as a New User. It was
     designed to tell the New User the rules of the System, etc.

     Example:

     TEXT NOABORT
     {1}

                                New User Information
                                --------------------

     This BBS supports only the Atari ST brand of computers.  If you do not  use
     or  own an Atari ST computer but would still like to join the BBS,  do  not
     request  or expect support for other computers.  My time and resources  are
     limited.  Since this is also a support board for Transcendence BBS program,
     I need the available space for support also.

     {38}
     There  will  be  NO illegal actions used  on  this  board.  This  includes,
     phreaking,  uploading commercial software,  etc.  Any illegal activity WILL
     result  in  the  termination of your user account and  you  will  be  Black
     Listed.  If  I  find resonable causes,  I may also turn your name  over  to
     someone that can do something about it.  I enjoy using my computer too much
     to  have  it taken away from me.  The E-mail WILL be scanned on  a  regular
     basis.  By joining this BBS,  you accept the fact that your E-Mail will  be
     read by me. I retain that right, especially since it is MY computer. If you
     have a problem with this, then hangup NOW.

     {47}

     NT_x_y.TXT

     If you have a command that only runs certain times of the day or
     certain days of the week and the user selects this option, then the
     BBS will display this file. x represents the Key and y represents the
     Page. The Main Menu is Page 1, the File Area Menu is Page 2 and the
     Message base Menu is page 3. For instance, say you only had Online
     Games on from 10:00:00 - 18:00:00 and the 'O' key defined as the key
     to press to access the Online Games from the Main Menu, and a user
     tried to access the Online Games area outside of this time frame, then
     the BBS will look for the file NT_O_1.TXT. In this file, you could
     just tell the user that the Online Games are available from 10:00:00 -
     18:00:00 (10am - 6pm). This also applies to the days of the week.

     Example:

     The Online Games are only available Saturday and Sunday.











                                     - 98 -


     OFF.TXT

     COMMAND: OFF

     This file is displayed when a user chooses this command. You will need
     to set up a Key in the Command Tables to make use of this Command or
     make use of it from a Menu File. This was designed as a quick way to
     logoff but it can also be used as below.

     Example:

     MENU NOABORT
     Selection:
     3
     1 p MAIL_1 N
     Q p OFFNOT N
     DEFAULT exit

     Logoff Options:
     [=]=[=]=[=]=[=]

     [1] Leave feedback to Wayne Watson
     [Q] Abort logoff
     [Return] to hangup

     OFFxx.TXT

     COMMAND: OFF

     This file is the same as the OFF.TXT file except it is another file in
     the sequence. You can have up to 99 OFFxx.TXT files.





























                                     - 99 -


     PARMEDIT.TXT

     COMMAND: PARMEDIT

     This file is displayed when the user chooses the PARMEDIT option. It
     was designed to allow the user to change their parameters, etc.

     Example:

     {1}

     Southern Software's Parm Editor
     -------------------------------
     [A] Real Name     : {3}
     [B] Handle/Alias  : {2}
     [C] Street Address: {5}
     [D] City          : {6}
     [E] State         : {58}
     [F] Zip Code      : {7}
     [G] Phone Number 1: {8}
     [H] Phone Number 2: {97}
     [I] Password      : {4}
     [J] Computer Types: {9}
     [K] Country       : {11}
     [L] Birth Date    : {12}
     [M] Video Width   : {14}
     [N] Video Length  : {15}
     [O] Sex           : {46}

     PASSWORD.TXT

     This file is displayed if you have the BBS setup as a Private BBS
     which is set in the System Editor. If this setting is on and there is
     a System Password defined, then the BBS will look for this file. In it
     you can tell the user that the BBS is reserved for your use or
     whatever.

     Example:

     Sorry, the BBS is locked for my use right now.  Please call later tonight.

                                                  The Sysop


















                                    - 100 -


     PROMPT.DAT

     This file contains the majority of the PROMPTS that the BBS uses. You
     can define how the prompts appear to the user, the wording that is
     used or whatever. You can even have VT52 codes, ANSI codes, etc. in
     this file. The only restriction is that you can only have up to 10
     lines for the prompt. Also, do NOT remove the '!' character between
     each prompt. The prompt begins after the '!' character. Example:

     ! (1)  Prompt 1
     The Prompt starts on the line after the !
     The Prompt ends on the line before the next !
     ! (2)  Prompt 2
     etc.

     If you want the cursor to stay on the same line as the prompt, then do
     not put a blank line at the end of the prompt. Scan through the
     PROMPT.DAT file for a look at how things are done and then run the BBS
     program and see the actual prompts being used. Just experiment with
     them to get the feel for how they are done.

     PROTOCOL.TXT

     This file is displayed anytime the BBS ask the user to choose a
     Protocol for File transfers. If this file is not found, then the BBS
     will use a built in display of the available Protocols. The selections
     in this file should match what is in the PROTOCOL.DAT file which can
     be edited in the System Editor.

     Example:

     {1}
                            Southern Software's Protocols
                            -----------------------------

                              [C] Xmodem Chksum
                              [F] Fmodem Batch
                              [G] Ymodem-G Batch (Not Yet)
                              [K] Xmodem 1K
                              [X] Xmodem CRC
                              [Y] Ymodem Batch
                              [Z] Zmodem Batch

                              [Q] Quit (Abort Transfer)
















                                    - 101 -


     RINGBACK.TXT

     COMMAND: RINGBACK

     This file will be displayed prior to the BBS hanging up on the user to
     call them back if they choose the Ringback feature and you have it
     enabled in the System Editor. It just explains what the BBS is about
     to do and gives the user instructions that they may need.

     Example:

     {1}Ringback
     [==========]

          Ringback will force the BBS to hang you up, and call you right back.
     This is often helpful for line noise, or those who have "Measured"
     service.
          Three attempts will be made to call you.  If those are not successful,
     the BBS will give up on you.
          There will be a short pause before the BBS calls you back.  During
     this time you should configure your modem to auto-answer incoming calls
     (If it isn't already).  To do this with a Hayes-Compatible modem send the
     command "ATS0=1" to the modem.

     {47}

     SYSNEWS.TXT

     This file is part of the LOGON sequence. It was designed to be used
     for any news from the Sysop, etc. You can set it up as a Menu File or
     whatever.

     Example:

     MENU
                                      Selection:
     7
     1 t J:\TEXT\MENUS0\SYSINFO.TXT
     2 t J:\UPDATES\UPDATES.TXT
     3 t J:\UPDATES\UE_UPD.TXT
     4 t J:\SYSEDITG.PTC\CHANGES.TXT
     5 t J:\TEXT\MENUS0\VERSIONS.TXT
     6 t J:\TEXT\ALTRNATE.TXT
     DEFAULT EXIT
     {1}                       Welcome to Southern Software

                          [1]  Latest System News
                          [2]  Update File for Transcendence BBS
                          [3]  Update File for User Editor
                          [4]  Update File for System Editor
                          [5]  Latest Version of Programs
                          [6]  Alternate Download Locations

                                    [RETURN] to Exit

     Above is an example of a Menu file for the System News. You can also
     have just a plain text file for the System news.



                                    - 102 -


     SYSNEWSxx.TXT

     This file is the same as the above SYSNEWS.TXT file except, it is just
     the next file in sequence to be displayed after the SYSNEWS.TXT file.
     You can have up to 99 SYSNEWSxx.TXT files.

     SYSONSYS.TXT

     This file is displayed to the user when the Sysop enters the Sysop
     Mode (Dos Shell) using the F1 function key and chooses the '<1> Send
     Msg' option.

     Example:

     I'm BUSY, just hold on a sec...

     SYSOPOUT.TXT

     COMMAND: CALLSYS

     This file is displayed when the user chooses the CALLSYS command to
     page the Sysop and Chat Mode is turned off.

     Example:

     I am at work, At the tone, [L]eave feedback and I will answer your mail
     when I get home.

     TERMINAL.TXT

     COMMAND: TERMINAL

     This file is displayed user chooses the TERMINAl command. It just
     displays the available emulation modes and what number they need to
     choose. The number the user chooses will cause the BBS to look in the
     MENUSx folder for files that are to be displayed to the user. The 'x'
     in MENUSx corresponds to the number the user chooses.

     Example:

     {1}Southern Software's Terminal Types
     ----------------------------------

          [0] - 80 Column ASCII
          [1] - VT52 Mono
          [2] - VT52 Color
          [3] - ANSI Color

     If the user chose 1, then the BBS would look in the MENUS1 folder for
     text files that you have defined. If the BBS does not find the file it
     is looking for, then it will look in the MENUS0 folder for the file.
     The BBS will always revert back to the MENUS0 folder if a file is not
     found in the currently selected MENUSx folder. In the above example,
     you would have text files setup with VT52 mono escape codes so that
     the files will show up properly with someone using a mono monitor and
     using VT52.




                                    - 103 -


     USERLIST.TXT

     COMMAND: USERLIST

     This file is displayed when the user chooses the USERLIST command. It
     is used to display the options available. If it is not found, the BBS
     will use a built in display of the options available.

     Example:

     Search Methods
     ==============

     [1] - Search by Name
     [2] - Search by City
     [3] - Search by State
     [4] - Search by Computer
     [5] - Search ALL

     USERPARM.TXT

     COMMAND: USTATS

     This file is displayed when the user chooses the USTATS command. It is
     designed to give the user an overview of their statistics. You can
     define whatever you want displayed. The USTATS command will also only
     allow the user to change their Password. This is different than the
     USERPARM command.

     Example:

     {1}Your Current Status:
     --------------------
     {3} (aka {2} #{17})
     {5}
     {6}, {58}  {7}
     {8}
     {97}

     Age       : {10p20} Sex      : {46}
     Computer  : {9p20} Password : {4}
     Country   : {11p20} Birthday : {12}
     First Call: {25p20} Last Call: {24}

     Messages Entered   : {13p10} Email Messages Entered: {16}
     Downloads          : {18p10} Uploads               : {19}
     UL:DL Ratio        : {20p10} Time Limit Per Day    : {21}
     Time Limit Per Call: {22p10} Time Used Today       : {23}
     Calls by you       : {26p10} Access Levels         : {29}/{45}/{86}/{87}
     Daily Call  Limit  : {49p10} Max. Email/Day        : {82}
     Max. Feedback/Day  : {83p10} Max. Pages/Call       : {84}
     Download Points    : {88p10} Number of "Hangups"   : {89}

     Notice the Variable Tag usage in this file. Below is a a list of the
     Variable Tags.





                                    - 104 -


     VERIFY.TXT

     This file is displayed to the user if you have the Auto-Verify option
     turned on in the System Editor and the user is a new user. It is used
     to explain to the user what is about to happen and how to react or
     setup their system so when the BBS calls them back, they will be setup
     to answer and enter the information requested by the BBS.

     Example:

     {1}Auto-Verify
     [============]

          This BBS will Automatically verify users by calling them back, and
     verifying their password.  This allows me, the Sysop, to know if you have
     provided me with a valid phone number.
          I am an understanding Sysop though, if you can not receive incoming
     calls for any reason then refuse the Verification process, and explain
     why in Email.
          To receive the incoming call send the command "ATS0=1" to your modem,
     after the BBS has terminated its connection with your modem.  The BBS will
     make three attempts to verify you, one right after the other.

     {47}

     WAITCALL.TXT

     This file is displayed when the BBS is at the WaitCall screen. This is
     the information at the top of the screen. If this file is not found,
     then the BBS will use the built in display of information.

     WELCOME.TXT

     This file is displayed upon connection right after the
     CONNECT.TXT/CONNEXTxx.TXT files.

     Example:

     TEXT NOABORT
     {1}
            [========================================================]

                         Welcome To a new Transcendence BBS

            [========================================================]

     WELCOMExx.TXT

     This file is basically the same as the WELCOME.TXT file except it is
     displayed in sequence after the WELCOME.TXT file. You can have up to
     99 WELCOMExx.TXT files.









                                    - 105 -


     VARIABLE TAGS

     Variable Tags allow the Sysop and in some instances the user, to place
     what is called a Variable Tag into a Text File, Menu File, Prompt
     file, etc. The BBS will then replace the {x} with the Data described
     below. These are used in files such as the EDITUSET.TXT file, etc.
     They are used for general purpose text files that will display the
     current data based on the user viewing the data, etc. Below is a list
     of all the Variable Tags used by the BBS and the information they
     provide. Each Variable Tag must be used in conjunction with braces as
     shown below.

     You can use a 'p' in a variable tag along with a number in order to
     pad the tag to so many spaces. This will keep the output of the tag to
     a set length. Example: {2p30} would always display the User's Handle
     at 30 characters in length. This helps to keep the output of a file
     lined up in columns.

     General Purpose Variable Tags

     These tags provide information about the user, to control the BBS,
     etc.

     {1}    Clears the Screen
     {2}    User's Handle
     {3}    User's Real name
     {4}    User's Password
     {5}    User's Address
     {6}    User's City
     {7}    User's Zip Code
     {8}    User's Voice Phone Number
     {9}    User's CPU
     {10}   User's Age
     {11}   User's Country
     {12}   User's Birthday
     {13}   Number of Messages Entered and number of Replies
     {14}   User's Video Width
     {15}   User's Video Length
     {16}   Number of Emails sent by user
     {17}   User's User Number
     {18}   User's number of Downloads
     {19}   User's number of Uploads
     {20}   User's DL:UL Ratio
     {21}   User's Time Limit per Day
     {22}   User's Time Limit per Call
     {23}   User's Time Used Today
     {24}   User's Last Call Date
     {25}   User's First Call Date
     {26}   User's number of Calls
     {27}   Today's Date  (01/19/93)
     {28}   Today's Date  (Jan. 19th, 1993)
     {29}   User's Command Table Level
     {30}   Number of Calls to System
     {31}   Last Caller
     {32}   Number of Calls Today
     {33}   Current Baud Rate of User
     {34}   Current Time
     {35}   User's Time Left for this Call
     {36}   User's Connect Time

                                    - 106 -


     {37}   Military Time
     {38}   Prompt for MORE
     {39}   Sysop's Name
     {40}   BBS Version number
     {41}   BBS Name
     {42}   BBS Node number
     {43}   Chat Mode Status
     {44}   Emails to you
     {45}   User's File Area Level
     {46}   User's Sex (M/F)
     {47}   Press Return Prompt
     {48}   Press Space prompt
     {49}   User's Daily Call Limit
     {50}   Not Used
     {51}   User's Downloads this Call
     {52}   User's Uploads this Call
     {53}   User's Downloads per Day Limit
     {54}   User's Uploads per Day Limit
     {55}   User's Downloads Today
     {56}   User's Uploads Today
     {57}   User's number of Calls Today
     {58}   User's State
     {59}   Number of User slots allocated
     {60}   Number of User slots in use
     {61}   Number of New Users
     {62}   Number of Surveys taken (NOT USED)
     {63}   User's number of Fmails sent
     {64}   User's number of Fmessages sent
     {65}   User's number of Games Played
     {66}   User's number of Feedback Messages sent
     {77}   Number of Messages entered on System
     {78}   Number of Emails entered on System
     {79}   Number of uploads to System
     {80}   Number of Downloads from System
     {81}   User's Alert Status (Alert! or Normal)
     {82}   User's Max Email per Day limit
     {83}   User's Max Messages per Day Limit
     {84}   User's Max Feedback per Day Limit
     {85}   User's Max Pages per day
     {86}   User's Online Game Level
     {87}   User's Menu Processor Level
     {88}   User's Download points
     {89}   User's number of Illegal Hangups
     {90}   User's last date of completing New Files Listing
     {91}   General Purpose BBS tag
     {92}   Event's ON time. Time system coming down for Event Scheduling.
     {93}   Name found during a partial name search in Email
     {94}   General Purpose BBS Tag. File Not Found.
     {95}   Number of Email entries TO user
     {96}   General Purpose BBS tag
     {97}   User's DATA Phone Number
     {98}   Number of seconds to pause output. (98-x) x = seconds
     {99}   User's Current Emulation in NUMBER format.







                                    - 107 -


     {100}  User's Current Emulation in TEXT format (VT52 Color)
     {101}  User's Default Terminal (Emulation) Type
     {102}  User's Default Window size (Sysop Only) in Text format
     {103}  User's Auto-Email setting
     {104}  User's Page Pause setting
     {105}  User's Hotkey setting
     {106}  User's Command Stack Printing setting
     {107}  User's Clear Screen setting
     {108}  User's Default Archive Type setting
     {109}  User's Continuous Message Scroll setting
     {110}  User's Pause Time between Messages setting
     {111}  User's File Area Prompt setting (long or Short)
     {112}  User's Message Base Prompt setting (long or short)
     {113}  User's Word Wrap in Editor setting
     {114}  User's Line Numbers in Editor setting
     {115}  User's Scan Mark Message Base setting
     {116}  User's Editor Summary setting
     {117}  User's Auto Quickscan New Messages setting
     {118}  User's Auto Quickscan New Files setting
     {119}  User's Emacs Editing setting
     {120}  User's New Files Scan setting (Catalog or Long listing)
     {121}  User's Key Aborts Text setting
     {122}  Banners Prompt  (Displays Random Banner)
     {123}  Banners Prompt  (Displays Currently Loaded Banner)
     {124}  Destructive Backspace. (124-x) x = number of backspaces to use
     {125}  Non-Destructive Backspace. (125-x) x = # of backspaces to use
     {126}  User's Current Information location in protected Memory

     {127-136}  Not Currently used

     The next few Tags were designed to be used in the Who's Called listing
     which uses the CALLS.TXT file for output of the last 'x' number of
     callers. The number of callers to display is set up in the System
     Editor.

     {137}  Caller number
     {138}  Handle
     {139}  Call Date
     {140}  Baud rate
     {141}  Connect Time
     {142}  Logoff Time

     Tags {1000}  -  {1100}  are Sysop definable Tags. You can have up to 100
     tags defined in DEF_TAGS.DAT which goes in the DATA folder. Refer to
     the description of this file in the DATA Files section.















                                    - 108 -


     Message Base Variable Tags

     These tags provide information about the Current Message Base and
     currently selected Message.

     {200}  Message Base Number
     {201}  Message Number
     {202}  Lines in Current Message
     {203}  Message Base name
     {204}  From (handle)
     {205}  To (handle)
     {206}  Date Message was posted
     {207}  Time Message was posted
     {208}  Subject of Message
     {209}  Number of replies to Message
     {210}  Message's Status in Text format (Normal, Extended, etc.)
     {211}  Number of New Messages to user in selected Message Base
     {212}  User's highest Message Read in selected Message Base
     {213}  Max number of Messages that can be entered on selected Msg Base
     {214}  Max number of Lines that can be entered on selected Msg Base
     {215}  User's highest Message read in selected Message Base
     {216}  Message Number this Message is a reply to
     {217}  Date Message was read by TO user
     {218}  Time message was read by TO user

     File Area Variable tags

     These tags provide information about the File Area and currently
     selected File.

     {300}  File Area Number
     {301}  File Area Name
     {302}  Number of Files Marked for Batch DL
     {303}  Filename of selected File
     {304}  Filesize of selected File
     {305}  Program Type of selected File
     {306}  Uploader of selected File
     {307}  Upload Time of selected File
     {308}  Upload Date of selected File
     {309}  Last Downloaded Date of selected File
     {310}  Number of Downloads of selected File
     {311}  File Level of selected File
     {312}  File Status of selected File
     {313}  CPU Type of selected File
     {314}  Monitor Type of selected File
     {315}  File Description of selected File
     {316}  Approx. Time to Download at {33}  Baud Rate of selected File
     {317}  Used for a Blank Space
     {318}  User's Default Protocol
     {319}  User's currently selected Protocol
     {320}  Number of Descriptions/Files in File Area
     {321}  Approx. Time to Download Marked Files
     {322}  File Number of selected File
     {323}  Not Used
     {324}  Xmodem Blocks of selected File
     {325}  Y/Zmodem Blocks of selected File
     {326}  Fmodem Blocks of selected File
     {327}  CPS Rating of downloaded File(s)


                                    - 109 -


     {328}  Old Filename. Used during File Renames
     {329}  New Filename. "                      "
     {330}  Max number of allowed Uploads
     {331}  Max Upload Size. Most available Space on Drive.
     {332}  File Type of selected File
     {333}  Used for Questions when Editing File or entering Description
     {334}  Brief Description of selected File
     {335}  Catalog Letter Choice




















































                                    - 110 -